From: Petr Baudis Date: Tue, 05 Jul 2005 09:34:41 GMT Subject: Re: [PATCH] Add script for patch submission via e-mail. Message-ID: <20050705093441.GD6191@pasky.ji.cz> In-Reply-To: <7vll5h7k5t.fsf@assigned-by-dhcp.cox.net> Dear diary, on Sat, Jun 11, 2005 at 03:32:30AM CEST, I got a letter where Junio C Hamano told me that... > This git-format-patch-script is what I use to prepare patches > for e-mail submission. > > Typical usage is: > > $ git-format-patch-script -B -C --find-copies-harder HEAD linus > > to prepare each commit with its patch since "HEAD" forked from > "linus", one file per patch for e-mail submission. Each output > file is numbered sequentially from 1, and uses the first line of > the commit message (massaged for pathname safety) as the > filename. > > $ git-format-patch-script -B -C --find-copies-harder HEAD linus .patch/ > > creates output files in .patch/ directory. > > Signed-off-by: Junio C Hamano > --- > *** Linus I am submitting this one because some patches on > *** read-tree I am going to send you will need this for > *** formatting into a form that is easier to review. And this > *** in turn can use diff-tree --find-copies-harder, which I > *** indeed used to generate the patches that follow. Any reason why this was not applied? It appears kind of cool. Well, I will probably take it and extend cg-mkpatch with it so I don't need it in Git, but I'm so altruistic and want to bring at least a bit of light to the gloomy dark world of the poor core Git plumbing users. ;-) -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ be careful, some twit might quote you out of context..