<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/git-octopus-script, branch gitk-resize-error</title>
<subtitle>Fork of git SCM with my patches.</subtitle>
<id>http://git.kilabit.info/git/atom?h=gitk-resize-error</id>
<link rel='self' href='http://git.kilabit.info/git/atom?h=gitk-resize-error'/>
<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>[PATCH] Infamous 'octopus merge'</title>
<updated>2005-08-24T23:50:51Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-08-20T09:58:42Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=d9f3be7e2e4c9b402bbe6ee6e2b39b2ee89132cf'/>
<id>urn:sha1:d9f3be7e2e4c9b402bbe6ee6e2b39b2ee89132cf</id>
<content type='text'>
This script uses the list of heads and their origin multi-head "git
fetch" left in the $GIT_DIR/FETCH_HEAD file, and makes an octopus
merge on top of the current HEAD using them.

The implementation tries to be strict for the sake of safety.  It
insists that your working tree is clean (no local changes) and matches
the HEAD, and when any of the merged heads does not automerge, the
whole process is aborted and tries to rewind your working tree is to
the original state.

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