<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/git-merge-recursive.py, branch v0.99.8a</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v0.99.8a</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v0.99.8a'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2005-10-02T17:03:00Z</updated>
<entry>
<title>[PATCH] Teach the recursive merge strategy about renames.</title>
<updated>2005-10-02T17:03:00Z</updated>
<author>
<name>Fredrik Kuivinen</name>
<email>freku045@student.liu.se</email>
</author>
<published>2005-10-02T15:43:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=af215114f52af0f308ef19f67e544df8ea5e4ac2'/>
<id>urn:sha1:af215114f52af0f308ef19f67e544df8ea5e4ac2</id>
<content type='text'>
It will now merge cases where a file was renamed in one branch and
modified in the other branch cleanly. We also detect a couple of
conflict cases now that wasn't detected before.

Signed-off-by: Fredrik Kuivinen &lt;freku045@student.liu.se&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] recursive-merge: Don't print a stack trace when read-tree fails.</title>
<updated>2005-09-25T23:08:53Z</updated>
<author>
<name>Fredrik Kuivinen</name>
<email>freku045@student.liu.se</email>
</author>
<published>2005-09-25T14:48:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=0bed18998ae6c0cec1485e6295be16a4fcebc7a7'/>
<id>urn:sha1:0bed18998ae6c0cec1485e6295be16a4fcebc7a7</id>
<content type='text'>
If the working tree is dirty read-tree will fail, and we don't want an
ugly stack trace in that case. Also make sure we don't print stack
traces when we use 'die'.

Signed-off-by: Fredrik Kuivinen &lt;freku045@student.liu.se&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-merge-recursive: Trivial RE fixes.</title>
<updated>2005-09-14T04:09:03Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-09-14T04:09:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=74376a686425c6304eafff9f26d8d5fb0d083bc0'/>
<id>urn:sha1:74376a686425c6304eafff9f26d8d5fb0d083bc0</id>
<content type='text'>
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] Use a temporary index file when we merge the common ancestors.</title>
<updated>2005-09-13T22:45:25Z</updated>
<author>
<name>Fredrik Kuivinen</name>
<email>freku045@student.liu.se</email>
</author>
<published>2005-09-13T21:41:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=6511cce24b932eba33d8e13b54664673121a8b7e'/>
<id>urn:sha1:6511cce24b932eba33d8e13b54664673121a8b7e</id>
<content type='text'>
With this change we can get rid of a call to 'git-update-index
--refresh'.

Signed-off-by: Fredrik Kuivinen &lt;freku045@student.liu.se&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] Adjust git-merge-recursive.py for the new tool names.</title>
<updated>2005-09-13T22:45:25Z</updated>
<author>
<name>Fredrik Kuivinen</name>
<email>freku045@student.liu.se</email>
</author>
<published>2005-09-13T21:40:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=87a71b65acc10c4879b13d2030185e5640a087cd'/>
<id>urn:sha1:87a71b65acc10c4879b13d2030185e5640a087cd</id>
<content type='text'>
Signed-off-by: Fredrik Kuivinen &lt;freku045@student.liu.se&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] Don't output 'Automatic merge failed, ...'</title>
<updated>2005-09-13T22:45:24Z</updated>
<author>
<name>Fredrik Kuivinen</name>
<email>freku045@student.liu.se</email>
</author>
<published>2005-09-13T21:40:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=0d214b6619bf14a6409a2a1ba079f3530d40ee41'/>
<id>urn:sha1:0d214b6619bf14a6409a2a1ba079f3530d40ee41</id>
<content type='text'>
git-merge.sh does this for us.

Signed-off-by: Fredrik Kuivinen &lt;freku045@student.liu.se&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] Be more like the 'resolve' strategy.</title>
<updated>2005-09-13T22:45:23Z</updated>
<author>
<name>Fredrik Kuivinen</name>
<email>freku045@student.liu.se</email>
</author>
<published>2005-09-13T21:39:34Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d9a23fa6f7124befe7803f5f3a8c53999578caa4'/>
<id>urn:sha1:d9a23fa6f7124befe7803f5f3a8c53999578caa4</id>
<content type='text'>
If there are non-mergeable changes leave the head contents in the
cache and update the working directory with the output from merge(1).

In the add/add and delete/modify conflict cases leave unmerged cache
entries in the index.

Signed-off-by: Fredrik Kuivinen &lt;freku045@student.liu.se&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] Rename the 'fredrik' merge strategy to 'recursive'.</title>
<updated>2005-09-13T07:20:54Z</updated>
<author>
<name>Fredrik Kuivinen</name>
<email>freku045@student.liu.se</email>
</author>
<published>2005-09-13T06:22:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e4cf17ce0db2dab7c9525a732f86c5e3df3b4ed0'/>
<id>urn:sha1:e4cf17ce0db2dab7c9525a732f86c5e3df3b4ed0</id>
<content type='text'>
Otherwise we would regret when Fredrik comes up with another merge
algorithm with different pros-and-cons with the current one.

Signed-off-by: Fredrik Kuivinen &lt;freku045@student.liu.se&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
</feed>
