<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/git-am.sh, branch v1.3.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v1.3.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v1.3.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2006-05-02T19:42:12Z</updated>
<entry>
<title>Give the user a hint for how to continue in the case that git-am fails because it requires user intervention</title>
<updated>2006-05-02T19:42:12Z</updated>
<author>
<name>Robert Shearman</name>
<email>rob@codeweavers.com</email>
</author>
<published>2006-05-02T12:32:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ced9456a27197fc038fbc5b5ebad87e55f1920d2'/>
<id>urn:sha1:ced9456a27197fc038fbc5b5ebad87e55f1920d2</id>
<content type='text'>
Give the user a hint for how to continue in the case that git-am fails
because it requires user intervention.

Signed-off-by: Robert Shearman &lt;rob@codeweaves.com&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-am --resolved: more usable error message.</title>
<updated>2006-04-28T09:32:44Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2006-04-28T09:32:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=c1d1128bef97ae16a6740538abe5fb81c67ed239'/>
<id>urn:sha1:c1d1128bef97ae16a6740538abe5fb81c67ed239</id>
<content type='text'>
After doing the hard work of hand resolving the conflicts in the
working tree, if the user forgets to run update-index to mark
the paths that have been resolved, the command gave an
unfriendly "fatal: git-write-tree: not able to write tree" error
message.  Catch the situation early and give more meaningful
message and suggestion.

Noticed and suggested by Len Brown.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>war on whitespaces: documentation.</title>
<updated>2006-03-02T08:52:59Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2006-03-02T08:45:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8273c79ae2e6b782dba3dccb815b386cc83e4294'/>
<id>urn:sha1:8273c79ae2e6b782dba3dccb815b386cc83e4294</id>
<content type='text'>
We were missing the --whitespace option in the usage string for
git-apply and git-am, so this commit adds them.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-am: --whitespace=x option.</title>
<updated>2006-03-01T06:34:57Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2006-03-01T04:26:25Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8c31cb822f387d7bc51b51cbacd08d62faed4faa'/>
<id>urn:sha1:8c31cb822f387d7bc51b51cbacd08d62faed4faa</id>
<content type='text'>
This is passed down to git-apply to override the built-in
default and per-repository configuration at runtime.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-am: do not allow empty commits by mistake.</title>
<updated>2006-02-24T06:14:47Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2006-02-24T06:14:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=6d28644d691fa3967d24d988d51d863f22bbcc63'/>
<id>urn:sha1:6d28644d691fa3967d24d988d51d863f22bbcc63</id>
<content type='text'>
Running "git-am --resolved" without doing anything can create an empty
commit. Prevent it.

Thanks for Eric W. Biederman for spotting this.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Keep Porcelainish from failing by broken ident after making changes.</title>
<updated>2006-02-22T21:14:57Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2006-02-19T04:51:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d64e6b04291e2313343866a6b206caf13313f1f9'/>
<id>urn:sha1:d64e6b04291e2313343866a6b206caf13313f1f9</id>
<content type='text'>
"empty ident not allowed" error makes commit-tree fail, so we
are already safer in that we would not end up with commit
objects that have bogus names on the author or committer fields.
However, before commit-tree is called there are already changes
made to the index file and the working tree.  The operation can
be resumed after fixing the environment problem, but when this
triggers to a newcomer with unusable gecos, the first question
becomes "what did I lose and how would I recover".

This patch modifies some Porcelainish commands to verify
GIT_COMMITTER_IDENT as soon as we know we are going to make some
commits before doing much damage to prevent confusion.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Only call git-rerere if $GIT_DIR/rr-cache exists.</title>
<updated>2006-02-12T02:55:43Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2006-02-12T02:55:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=1536dd9c61b5582cf079999057cb715dd6dc6620'/>
<id>urn:sha1:1536dd9c61b5582cf079999057cb715dd6dc6620</id>
<content type='text'>
Johannes noticed that git-rerere depends on Digest.pm, and if
one does not use the command, one can live without it.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-rerere: reuse recorded resolve.</title>
<updated>2006-02-07T05:53:11Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2006-01-29T07:15:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8389b52b2a51d5b110b508cc67f0f41f99c30d3f'/>
<id>urn:sha1:8389b52b2a51d5b110b508cc67f0f41f99c30d3f</id>
<content type='text'>
In a workflow that employs relatively long lived topic branches,
the developer sometimes needs to resolve the same conflict over
and over again until the topic branches are done (either merged
to the "release" branch, or sent out and accepted upstream).

This commit introduces a new command, "git rerere", to help this
process by recording the conflicted automerge results and
corresponding hand-resolve results on the initial manual merge,
and later by noticing the same conflicted automerge and applying
the previously recorded hand resolution using three-way merge.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Fix git-am --skip</title>
<updated>2005-12-17T06:28:19Z</updated>
<author>
<name>Jan Harkes</name>
<email>jaharkes@cs.cmu.edu</email>
</author>
<published>2005-12-17T06:01:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=69224716f78d6a772318e73060a70ba5ae67e55b'/>
<id>urn:sha1:69224716f78d6a772318e73060a70ba5ae67e55b</id>
<content type='text'>
git-am --skip does not unpack the next patch and ends up reapplying the
old patch, believing that it is the new patch in the sequence.

If the old patch applied successfully it will commit it with the
supposedly skipped log message and ends up dropping the following patch.
If the patch did not apply the user is left with the conflict he tried
to skip and has to unpack the next patch in the sequence by hand to get
git-am back on track.

By clearing the resume variable whenever skips bumps the sequence
counter we correctly unpack the next patch. I also added another
resume= in the case a patch file is missing from the sequence to
avoid the same problem when a file in the sequence was removed.

Signed-off-by: Jan Harkes &lt;jaharkes@cs.cmu.edu&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>mailinfo and git-am: allow "John Doe &lt;johndoe&gt;"</title>
<updated>2005-12-15T00:31:06Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-12-15T00:31:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e0e3ba208d235ab5623a86204fbd20b449520764'/>
<id>urn:sha1:e0e3ba208d235ab5623a86204fbd20b449520764</id>
<content type='text'>
An isolated developer could have a local-only e-mail, which will
be stripped out by mailinfo because it lacks '@'.  Define a
fallback parser to accomodate that.

At the same time, reject authorless patch in git-am.

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