Git am is giving me trouble.Im a gmail user, and have saved a patch series by doingshow-original, save w rename for each patchgit apply mail-1-11.txt works,but it disregards the commit-msg, so commit-ids are lost,(I could attempt to checkin each with cut-paste commit-msgs,but this sounds like a losing game)and patchset isnt trackable as such.grabbing diffs from lkml.org site doesnt help,since theyre raw diffs, theyre lacking the commit-msg.have I missed an option, or is am's format detection less than it should be?Ive attached mail-1-11, which applies cleanly to v3.0, but wont am. On Sat, Aug 13, 2011 at 01:49:35PM -0600, Jim Cromie wrote: git am is giving me trouble. Im a gmail user, and have saved a patch series by doing show-original, save w rename for each patch snipMy experience with gmail + patches is that you need to use anemail client to download patches, not the web interface.mutt works well for me. Any client that can talk to gmailover imaps:// should do the trick.I couldn't find what was wrong with the patch youattached to your original message, though.-David-To unsubscribe from this list: send the line 'unsubscribe git' inthe body of a message toMore majordomo info at. Hi Jim,+CC: David BarrJim Cromie writes: git am is giving me trouble.
Im a gmail user, and have saved a patch series by doing show-original, save w rename for each patch. Ive attached mail-1-11, which applies cleanly to v3.0, but wont am.It works quite well for me after David's recent patch: 0e8341f2 (am:ignore leading whitespace before patch, 2011-08-08). The patch hasalready made it to 'next', but hasn't hit 'master' yet. Could youplease try it and tell us if there are any issues?Thanks.- Ram-To unsubscribe from this list: send the line 'unsubscribe git' inthe body of a message toMore majordomo info at. Hi Jim, +CC: David Barr Jim Cromie writes: git am is giving me trouble. Im a gmail user, and have saved a patch series by doing show-original, save w rename for each patch. Ive attached mail-1-11, which applies cleanly to v3.0, but wont am.
Git Apply Patch Format Detection Failed
It works quite well for me after David's recent patch: 0e8341f2 (am: ignore leading whitespace before patch, 2011-08-08). The patch has already made it to 'next', but hasn't hit 'master' yet.