<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/git-rebase-script, branch main</title>
<subtitle>Fork of git SCM with my patches.</subtitle>
<id>http://git.kilabit.info/git/atom?h=main</id>
<link rel='self' href='http://git.kilabit.info/git/atom?h=main'/>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/'/>
<updated>2005-09-08T00:45:20Z</updated>
<entry>
<title>Big tool rename.</title>
<updated>2005-09-08T00:45:20Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-09-08T00:26:23Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=215a7ad1ef790467a4cd3f0dcffbd6e5f04c38f7'/>
<id>urn:sha1:215a7ad1ef790467a4cd3f0dcffbd6e5f04c38f7</id>
<content type='text'>
As promised, this is the "big tool rename" patch.  The primary differences
since 0.99.6 are:

  (1) git-*-script are no more.  The commands installed do not
      have any such suffix so users do not have to remember if
      something is implemented as a shell script or not.

  (2) Many command names with 'cache' in them are renamed with
      'index' if that is what they mean.

There are backward compatibility symblic links so that you and
Porcelains can keep using the old names, but the backward
compatibility support  is expected to be removed in the near
future.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Redo "revert" using three-way merge machinery.</title>
<updated>2005-08-29T19:52:02Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-08-28T06:53:27Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=48313592bf318139b39d6017a863f27420e3939a'/>
<id>urn:sha1:48313592bf318139b39d6017a863f27420e3939a</id>
<content type='text'>
The reverse patch application using "git apply" sometimes is too
rigid.  Since the user would get used to resolving conflicting merges
by hand during the normal merge experience, using the same machinery
would be more helpful rather than just giving up.

Cherry-picking and reverting are essentially the same operation.
You pick one commit, and apply the difference that commit introduces
to its own commit ancestry chain to the current tree.  Revert applies
the diff in reverse while cherry-pick applies it forward.  They share
the same logic, just different messages and merge direction.

Rewrite "git rebase" using "git cherry-pick".

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Also make git-rebase-script stricter about dirty working tree.</title>
<updated>2005-08-18T23:30:36Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-08-18T23:30:36Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=a8055f8a8ed10a6d3272382f38a0808427ab4921'/>
<id>urn:sha1:a8055f8a8ed10a6d3272382f38a0808427ab4921</id>
<content type='text'>
Otherwise the first commit rebase makes could include whatever
dirty state the original working tree had.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Stupid typo fix for git rebase.</title>
<updated>2005-08-18T20:00:53Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-08-18T20:00:53Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=66e06b6a17f1074401ad23f4b2a8a146b2900333'/>
<id>urn:sha1:66e06b6a17f1074401ad23f4b2a8a146b2900333</id>
<content type='text'>
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Make rebase script saner.</title>
<updated>2005-08-17T22:19:57Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-08-17T22:19:57Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=99a92f928fd02a87d841a8bb19511e7ce526819d'/>
<id>urn:sha1:99a92f928fd02a87d841a8bb19511e7ce526819d</id>
<content type='text'>
It did not check to see if the working tree was clean and matched
the commit we were starting out as, resulting in the initial rebased
commit including whatever dirty state the working tree has had.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Audit rev-parse users.</title>
<updated>2005-08-15T22:37:37Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-08-15T22:37:37Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=2ad77e67c7c95982ebc9b99ee6a2d007feada62e'/>
<id>urn:sha1:2ad77e67c7c95982ebc9b99ee6a2d007feada62e</id>
<content type='text'>
Make sure that we say --verify when we want to get a single SHA1
name.  Also when we say --verify, --revs-only is redundant.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Teach format-patch, rebase and cherry a..b format</title>
<updated>2005-08-10T06:38:50Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-08-07T22:51:09Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=4282c4fbddfeae3383c6c327e2ca98b25500ea31'/>
<id>urn:sha1:4282c4fbddfeae3383c6c327e2ca98b25500ea31</id>
<content type='text'>
Although these commands take only begin and end, not necessarily
generic SHA1 expressions rev-parse supports, supporting a..b
notation is good for consistency.  This commit adds such without
breaking backward compatibility.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-commit: log parameter updates.</title>
<updated>2005-08-10T05:28:22Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-08-09T00:03:14Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=0c091296c001836e408b8c98de1548d6c7ada67d'/>
<id>urn:sha1:0c091296c001836e408b8c98de1548d6c7ada67d</id>
<content type='text'>
While moving '-m' to make room for CVS compatible "here is the
log message", enhance source of log parameters.

  -m 'message': a command line parameter.
  -F &lt;file&gt;   : a file (use '-' to read from stdin).
  -C &lt;commit&gt; : message in existing commit.
  -c &lt;commit&gt; : message in existing commit (allows further editing).

Longer option names for these options are also available.

While we are at it, get rid of shell array bashism.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] Audit rev-parse users.</title>
<updated>2005-07-23T03:34:16Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-07-23T02:09:05Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=f6e1a4d6dc4d1b3d82d5e87fdd817b3994dda5e0'/>
<id>urn:sha1:f6e1a4d6dc4d1b3d82d5e87fdd817b3994dda5e0</id>
<content type='text'>
This patch changes rev-parse users that pass a single argument
that is supposed to be a rev parameter to use "--verify".

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] git-rebase-script: rebase local commits to new upstream head.</title>
<updated>2005-06-25T23:52:16Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-06-25T09:23:43Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=59e6b23acef9d29b9bdabc38ee80361e19ef7ebe'/>
<id>urn:sha1:59e6b23acef9d29b9bdabc38ee80361e19ef7ebe</id>
<content type='text'>
Using git-cherry, forward port local commits missing from the
new upstream head.  This also depends on "-m" flag support in
git-commit-script.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
</feed>
