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
- reads
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
- reads
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 'from' in
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 clarification! I
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 intend
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. ;-)
It
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
7 matches
Mail list logo
