<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git, branch v1.6.6-rc1</title>
<subtitle>Fork of git SCM with my patches.</subtitle>
<id>http://git.kilabit.info/git/atom?h=v1.6.6-rc1</id>
<link rel='self' href='http://git.kilabit.info/git/atom?h=v1.6.6-rc1'/>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/'/>
<updated>2009-12-02T18:50:17Z</updated>
<entry>
<title>Git 1.6.6-rc1</title>
<updated>2009-12-02T18:50:17Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2009-12-02T18:50:17Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=b809d9cd0787e68f442c6795ec76580bb37d1a00'/>
<id>urn:sha1:b809d9cd0787e68f442c6795ec76580bb37d1a00</id>
<content type='text'>
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-pull.sh: Fix call to git-merge for new command format</title>
<updated>2009-12-02T18:42:48Z</updated>
<author>
<name>Horst H. von Brand</name>
<email>vonbrand@inf.utfsm.cl</email>
</author>
<published>2009-12-01T22:44:11Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=c0ecb07048ce2123589a2f077d296e8cf29a9570'/>
<id>urn:sha1:c0ecb07048ce2123589a2f077d296e8cf29a9570</id>
<content type='text'>
Now "git merge &lt;msg&gt; HEAD" is officially deprecated, we should
clean our own use as well.

Signed-off-by: Horst H. von Brand &lt;vonbrand@inf.utfsm.cl&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'maint'</title>
<updated>2009-12-02T18:30:12Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2009-12-02T18:30:12Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=0748494e866041034605aaf177f29a61bdc25951'/>
<id>urn:sha1:0748494e866041034605aaf177f29a61bdc25951</id>
<content type='text'>
* maint:
  Prepare for 1.6.5.4
  merge: do not add standard message when message is given with -m option
  Do not misidentify "git merge foo HEAD" as an old-style invocation

Conflicts:
	RelNotes
</content>
</entry>
<entry>
<title>Prepare for 1.6.5.4</title>
<updated>2009-12-02T18:29:00Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2009-12-02T18:29:00Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=28044baba6d268d91057398ffa041ee1b931a5e0'/>
<id>urn:sha1:28044baba6d268d91057398ffa041ee1b931a5e0</id>
<content type='text'>
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>merge: do not add standard message when message is given with -m option</title>
<updated>2009-12-02T18:02:08Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2009-12-02T18:00:58Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=ce9d823b9141756b5e60aa6c62653adb08e7213b'/>
<id>urn:sha1:ce9d823b9141756b5e60aa6c62653adb08e7213b</id>
<content type='text'>
Even if the user explicitly gave her own message to "git merge", the
command still added its standard merge message.  It resulted in a
useless repetition like this:

    % git merge -m "Merge early part of side branch" `git rev-parse side~2`
    % git show -s
    commit 37217141e7519629353738d5e4e677a15096206f
    Merge: e68e646 a1d2374
    Author: しらいし ななこ &lt;nanako3@lavabit.com&gt;
    Date:   Wed Dec 2 14:33:20 2009 +0900

	Merge early part of side branch

	Merge commit 'a1d2374f8f52f4e8a53171601a920b538a6cec23'

The gave her own message because she didn't want git to add the
standard message (if she wanted to, she wouldn't have given one,
or she would have prepared it using git-fmt-merge-msg command).

Noticed by Nanako Shiraishi

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Do not misidentify "git merge foo HEAD" as an old-style invocation</title>
<updated>2009-12-02T18:01:59Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2009-12-02T17:59:35Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=76bf488e61b8a87191a1779b79820545e64ef275'/>
<id>urn:sha1:76bf488e61b8a87191a1779b79820545e64ef275</id>
<content type='text'>
This was misinterpreted as an ancient style "git merge &lt;message&gt; HEAD
&lt;commit&gt; &lt;commit&gt;..." that merges one (or more) &lt;commit&gt; into the current
branch and record the resulting commit with the given message.  Then a
later sanity check found that there is no &lt;commit&gt; specified and gave
a usage message.

Tested-by: Nanako Shiraishi &lt;nanako3@lavabit.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Update draft release notes to 1.6.6 before -rc1</title>
<updated>2009-12-01T20:50:23Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2009-11-30T23:54:08Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=c86485dd15d54fc6ff2cd0dda3b2a9faa4f2d66e'/>
<id>urn:sha1:c86485dd15d54fc6ff2cd0dda3b2a9faa4f2d66e</id>
<content type='text'>
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'maint'</title>
<updated>2009-12-01T20:47:04Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2009-12-01T20:47:04Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=32ef08f4e5ab6ce8f3b47201f1df46d1a33deb80'/>
<id>urn:sha1:32ef08f4e5ab6ce8f3b47201f1df46d1a33deb80</id>
<content type='text'>
* maint:
  help: Do not unnecessarily look for a repository
  Documentation: Fix a few i.e./e.g. mix-ups
  Documentation: Document --branch option in git clone synopsis
</content>
</entry>
<entry>
<title>Merge branch 'jc/deprecate-old-syntax-from-merge'</title>
<updated>2009-12-01T20:47:01Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2009-12-01T20:47:01Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=36a83f375bc247a09f46de0445a138d5e6de8a4f'/>
<id>urn:sha1:36a83f375bc247a09f46de0445a138d5e6de8a4f</id>
<content type='text'>
* jc/deprecate-old-syntax-from-merge:
  git-merge: a deprecation notice of the ancient command line syntax
</content>
</entry>
<entry>
<title>git-merge: a deprecation notice of the ancient command line syntax</title>
<updated>2009-12-01T20:45:34Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2009-12-01T00:23:50Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=b81e00a965c62ca72a4b9db425ee173de147808d'/>
<id>urn:sha1:b81e00a965c62ca72a4b9db425ee173de147808d</id>
<content type='text'>
The ancient form of git merge command used in the original sample script
has been copied from Linus and are still found everywhere, I think, and
people may still have it in their scripts, but on the other hand, it is so
unintuitive that even people reasonably familiar with git are surprised by
accidentally triggering the support to parse this ancient form.

Gently nudge people to upgrade their script to more recent and readable
style for eventual removal of the original syntax.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
