On Thu, Jul 12, 2012 at 02:32:01PM -0400, Paul Gortmaker wrote: > In case it helps any, a brief summary of my workflow is this: > > git am /tmp/mbox > <some random fail halfway in the queue> > patch -p1 --dry-run < .git/rebase-apply/patch > # gauge status. Is patch really invalid, or already applied? > # already applied; "git am --skip" > # no, if valid, but with minor issues, apply what we can. > patch -p1 < .git/rebase-apply/patch > # manually deal with rejects (typically with wiggle) > git add any_new_files > git add -u > git am -r This does not in any way address your patch, but you may find it helpful. My usual next step after "git am" fails is to run "git am -3" and have it do a 3-way merge. This can sometimes resolve issues entirely, and when conflicts remain, they are placed in the file with the usual conflict markers (and the conflicted files are marked in the index, so you can even use "git mergetool" to help you run an external tool like xxdiff). -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html