On Thu, Oct 30, 2008 at 04:30:56PM +0000, Theodore Tso wrote: > 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. I've learned to > live with it, but it's annoying each time I have to do it. [...] > (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.) In fact I believe that what we lack is a shorthand for: $sha1^..$sha1 because that would solve both of your issues, and it's something that has bothered me in the past too for other commands. -- ·O· Pierre Habouzit ··O madcoder@xxxxxxxxxx OOO http://www.madism.org
Attachment:
pgp7oibPXvlTx.pgp
Description: PGP signature
