<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/git-am.sh, 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-12T02:55:43Z</updated>
<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>
<entry>
<title>Merge branch 'hold/am'</title>
<updated>2005-12-14T21:04:43Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-12-14T21:04:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=9a26dbd120110ad4e07d3047abc13d615183c8ec'/>
<id>urn:sha1:9a26dbd120110ad4e07d3047abc13d615183c8ec</id>
<content type='text'>
</content>
</entry>
<entry>
<title>git-am: Usage string clean-up</title>
<updated>2005-12-14T10:53:44Z</updated>
<author>
<name>freku045@student.liu.se</name>
<email>freku045@student.liu.se</email>
</author>
<published>2005-12-13T22:30:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=cf1fe88ce1fb75db14549e9d57d88c2ad88caf9d'/>
<id>urn:sha1:cf1fe88ce1fb75db14549e9d57d88c2ad88caf9d</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>git-am support for naked email messages (take 2)</title>
<updated>2005-12-14T10:04:56Z</updated>
<author>
<name>H. Peter Anvin</name>
<email>hpa@zytor.com</email>
</author>
<published>2005-12-14T06:39:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b3f041fb0f7de167dbb6711b0a231d36c4b5de08'/>
<id>urn:sha1:b3f041fb0f7de167dbb6711b0a231d36c4b5de08</id>
<content type='text'>
This allows git-am to accept single-message files as well as mboxes.
Unlike the previous version, this one doesn't need to be explicitly told
which one it is; rather, it looks to see if the first line is a From
line and uses it to select mbox mode or not.

I moved the logic to do all this into git-mailsplit, which got a new
user interface as result, although the old interface is still available
for backwards compatibility.

[jc: applied with two obvious fixes.]

Signed-off-by: H. Peter Anvin &lt;hpa@zytor.com&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Use printf rather than echo -n.</title>
<updated>2005-12-07T02:09:12Z</updated>
<author>
<name>Jason Riedy</name>
<email>ejr@EECS.Berkeley.EDU</email>
</author>
<published>2005-12-06T22:21:52Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=9754563ca9a99bc0fe233f43202af15704fbed4d'/>
<id>urn:sha1:9754563ca9a99bc0fe233f43202af15704fbed4d</id>
<content type='text'>
On AIX, there is no -n option to the system's echo.  Instead,
it needs the '\c' control character.  We could replace
  echo -n "foo"
with
  echo -e "foo\c"
but printf is recommended by most man pages.  Tested on AIX
5.3, Solaris 8, and Debian.

[jc: futureproofed two instances that uses variable with '%s'
 so later feeding different messages would not break things too
 easily; others are emitting literal so whoever changes the
 literal ought to notice more easily so they are safe.]

Signed-off-by: E. Jason Riedy &lt;ejr@cs.berkeley.edu&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-sh-setup: die if outside git repository.</title>
<updated>2005-11-25T21:49:17Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-11-24T08:12:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ae2b0f15180d4b044828c836bcab6a990efa5c8e'/>
<id>urn:sha1:ae2b0f15180d4b044828c836bcab6a990efa5c8e</id>
<content type='text'>
Now all the users of this script detect its exit status and die,
complaining that it is outside git repository.  So move the code
that dies from all callers to git-sh-setup script.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-am: --binary; document --resume and --binary.</title>
<updated>2005-11-18T06:36:31Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-11-17T00:46:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=087b6742fcab74f7a53626b98969bed27d288e2b'/>
<id>urn:sha1:087b6742fcab74f7a53626b98969bed27d288e2b</id>
<content type='text'>
Now git-apply can grok binary replacement patches, give --binary
flag to git-am.  As a safety measure, this is not by default
enabled, so that you do not let malicious e-mailed patch to
replace an arbitrary path with just a couple of lines (diff
index lines, the filename and string "Binary files "...) by
accident.

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