Theodore Tso <tytso@xxxxxxx> writes: > On Thu, Oct 30, 2008 at 03:43:21PM +0100, Pierre Habouzit wrote: >> >> git format-patch origin/next.. works already. I'm used to the asymetric >> git format-patch origin/next syntax, and I would be sorry if it >> disappeared though, and I see no really good reason to get rid of it. > > The reason why it annoys me is because I often what to cherry-pick a > single patch to send to someone, and so while "git show 332d2e78" > shows me the patch, but if I want to use git-send-email for that > particular patch, "git format-patch 332d2e78" doesn't DTRT. I have to > type "git format-patch 332d2e78^..332d2e78" instead. > ... > (And I get annoyed when I want to run git format-patch on a single > patch not at the tip of the tree; but if it's just me, I can write a > "git format-single-patch" wrapper script to get around it.) Huh? I am so used to "git format-patch -1 HEAD" (or "332d2e78") that I am very surprised. -- 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
