<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/apply.c, branch v1.2.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v1.2.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v1.2.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2006-02-04T07:35:14Z</updated>
<entry>
<title>Use sha1_file.c's mkdir-like routine in apply.c.</title>
<updated>2006-02-04T07:35:14Z</updated>
<author>
<name>Jason Riedy</name>
<email>ejr@EECS.Berkeley.EDU</email>
</author>
<published>2006-02-04T06:50:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8361e1d4d343a33a60145129dcf8c08ec7de84f2'/>
<id>urn:sha1:8361e1d4d343a33a60145129dcf8c08ec7de84f2</id>
<content type='text'>
As far as I can see, create_subdirectories() in apply.c just
duplicates the functionality of safe_create_leading_directories() from
sha1_file.c.  The former has a warm, fuzzy const parameter, but that's
not important.

The potential problem with EEXIST and creating directories should
never occur here, but will be removed by future
safe_create_leading_directories() changes.  Other uses of EEXIST in
apply.c should be fine barring intentionally malicious behavior.

Signed-off-by: Jason Riedy &lt;ejr@cs.berkeley.edu&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Make apply accept the -pNUM option like patch does.</title>
<updated>2006-02-01T00:22:01Z</updated>
<author>
<name>Daniel Barkalow</name>
<email>barkalow@iabervon.org</email>
</author>
<published>2006-01-31T05:36:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e36f8b6034f9df7e7b0aea912d1c8e850503623e'/>
<id>urn:sha1:e36f8b6034f9df7e7b0aea912d1c8e850503623e</id>
<content type='text'>
This only applies to traditional diffs, not to git diffs.

Signed-off-by: Daniel Barkalow &lt;barkalow@iabervon.org&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>fix potential deadlock in create_one_file</title>
<updated>2006-01-06T01:22:49Z</updated>
<author>
<name>Alex Riesen</name>
<email>raa.lkml@gmail.com</email>
</author>
<published>2006-01-05T09:00:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d9e08be9d5b632aed84d4ee870543babafe6614b'/>
<id>urn:sha1:d9e08be9d5b632aed84d4ee870543babafe6614b</id>
<content type='text'>
It can happen if the temporary file already exists (i.e. after a panic
and reboot).

Signed-off-by: Alex Riesen &lt;raa.lkml@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>trivial: O_EXCL makes O_TRUNC redundant</title>
<updated>2006-01-06T01:22:47Z</updated>
<author>
<name>Alex Riesen</name>
<email>raa.lkml@gmail.com</email>
</author>
<published>2006-01-05T08:58:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=781411ed46400f95c45c5ca103769288025b39d6'/>
<id>urn:sha1:781411ed46400f95c45c5ca103769288025b39d6</id>
<content type='text'>
Signed-off-by: Alex Riesen &lt;raa.lkml@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>xread/xwrite: do not worry about EINTR at calling sites.</title>
<updated>2005-12-20T02:28:16Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-12-20T00:18:28Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=1c15afb9343bca82e687d008ec983a9110ac9c40'/>
<id>urn:sha1:1c15afb9343bca82e687d008ec983a9110ac9c40</id>
<content type='text'>
We had errno==EINTR check after read(2)/write(2) sprinkled all
over the places, always doing continue.  Consolidate them into
xread()/xwrite() wrapper routines.

Credits for suggestion goes to HPA -- bugs are mine.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-apply: work from subdirectory.</title>
<updated>2005-11-29T07:13:01Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-11-26T07:14:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=edf2e37002eeb30a2ccad5db3b3e1fe41cdc7eb0'/>
<id>urn:sha1:edf2e37002eeb30a2ccad5db3b3e1fe41cdc7eb0</id>
<content type='text'>
When applying a patch to index file, we need to know where GIT_DIR is;
use setup_git_directory() to find it out.  This also allows us to work
from a subdirectory if we wanted to.

When git-apply is run from a subdirectory, it applies the given patch
only to the files under the current directory and below.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Deal with binary diff output from GNU diff 2.8.7</title>
<updated>2005-11-18T05:14:29Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-11-18T04:46:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=3200d1aee0c22a34d075aafefe3e92f4f7d08840'/>
<id>urn:sha1:3200d1aee0c22a34d075aafefe3e92f4f7d08840</id>
<content type='text'>
Some vintage of diff says just "Files X and Y differ\n", instead
of "Binary files X and Y differ\n", so catch both patterns.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>apply: allow-binary-replacement.</title>
<updated>2005-11-17T00:20:40Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-11-15T01:37:05Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=011f4274bbb14e44035586f2ede695d584b8cfd2'/>
<id>urn:sha1:011f4274bbb14e44035586f2ede695d584b8cfd2</id>
<content type='text'>
A new option, --allow-binary-replacement, is introduced.

When you feed a diff that records full SHA1 name of pre- and
post-image blob on its index line to git-apply with this option,
the post-image blob replaces the path if what you have in the
working tree matches the pre-image _and_ post-image blob is
already available in the object directory.

Later we _might_ want to enhance the diff output to also include
the full binary data of the post-image, to make this more
useful, but this is good enough for local rebasing application.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-apply: fail if a patch cannot be applied.</title>
<updated>2005-11-16T22:12:56Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-11-16T22:12:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=92927ed0aac56a86f85049215791fcd106af4b62'/>
<id>urn:sha1:92927ed0aac56a86f85049215791fcd106af4b62</id>
<content type='text'>
Recently we fixed 'git-apply --stat' not to barf on a binary
differences.  But it accidentally broke the error detection when
we actually attempt to apply them.

This commit fixes the problem and adds test cases.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>apply: fix binary patch detection.</title>
<updated>2005-11-15T01:15:07Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-11-15T01:15:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=9add69b1b1f76db874ed899c46fbe0b252aa3c23'/>
<id>urn:sha1:9add69b1b1f76db874ed899c46fbe0b252aa3c23</id>
<content type='text'>
The comparison to find "Binary files " string was looking at a
wrong place when offset != 0.

Also, we may have the full 40-byte textual sha1 on the index
line; two off-by-one errors prevented it.

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