Re: [PATCH 0/2] Update git-send-email-script with --compose

2005-09-05 Thread Junio C Hamano
Martin Langhoff <[EMAIL PROTECTED]> writes: > It shows that I was never familiar with the practices of linux > hackers. I've always read the references to mboxes holding patchbombs > meaning literally one mbox file with a zillion contatenated patches > received via email. To be fair to you, it is

Re: [PATCH 0/2] Update git-send-email-script with --compose

2005-09-05 Thread Martin Langhoff
On 9/6/05, Junio C Hamano <[EMAIL PROTECTED]> wrote: > Not really; --mbox output is one-file-per-patch and it is up to > you which ones to pick and concatenate them in what order, if you > want them in a single file. Hr. Then I better hide away in a little cave, and shut my big mouth up. ;-)

Re: [PATCH 0/2] Update git-send-email-script with --compose

2005-09-05 Thread Junio C Hamano
Martin Langhoff <[EMAIL PROTECTED]> writes: > Fair enough -- blame it on my primitive approach of only having 2 > working repositories, and having some patches in them that I'm not > pushing upstream. Exporting to mbox would mean that I have to edit the > mbox file to remove the patches I don't in

Re: [PATCH 0/2] Update git-send-email-script with --compose

2005-09-05 Thread Martin Langhoff
On 9/6/05, Junio C Hamano <[EMAIL PROTECTED]> wrote: > Ryan Anderson <[EMAIL PROTECTED]> writes: > > Sorry about that - I always export using git-format-patch using --mbox, > > and those work nicely. I'm a bit reluctant to do the [PATCH] fixup, but > > I think I will: Thanks Ryan for the clarific

Re: [PATCH 0/2] Update git-send-email-script with --compose

2005-09-05 Thread Junio C Hamano
Ryan Anderson <[EMAIL PROTECTED]> writes: > On Mon, Sep 05, 2005 at 11:16:57PM +1200, Martin Langhoff wrote: >> >> - reads "subject" from the first line of STDIN or file. If the line >> doesn't start with [PATCH it provides the [PATCH] prefix. I found it >> really confusing that it wants to get

Re: [PATCH 0/2] Update git-send-email-script with --compose

2005-09-05 Thread Ryan Anderson
On Mon, Sep 05, 2005 at 11:16:57PM +1200, Martin Langhoff wrote: > Ryan, > > is it possible to fix the git-send-email script to "just work" reading > in the emails that `git-format-patch-script -o patchdir origin` > generates? I have a very ugly local patch to git-send-email-script > that > > -

Re: [PATCH 0/2] Update git-send-email-script with --compose

2005-09-05 Thread Martin Langhoff
Ryan, is it possible to fix the git-send-email script to "just work" reading in the emails that `git-format-patch-script -o patchdir origin` generates? I have a very ugly local patch to git-send-email-script that - reads "from" from git-var, can be overridden by passing an explicit --from - rea

[PATCH 0/2] Update git-send-email-script with --compose

2005-09-04 Thread Ryan Anderson
As I promised Junio a few weeks ago (via private email), here's an update to git-send-email-script that fixes a few annoying things it does. 1. No longer require --subject for most uses. 2. No longer require --in-reply-to for most uses. 3. If not given as command line parameters, don't prompt fo