From: Christian Couder <chriscool@tuxfamily.org>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Michael J Gruber <git@drmicha.warpmail.net>,
Sverre Rabbelier <srabbelier@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, John Tapsell <johnflux@gmail.com>
Subject: Re: sending patch sets (was: Re: [PATCH 01/10] refs: add "for_each_bisect_ref" function)
Date: Fri, 27 Mar 2009 08:22:00 +0100 [thread overview]
Message-ID: <200903270822.01209.chriscool@tuxfamily.org> (raw)
In-Reply-To: <alpine.LNX.2.00.0903270126210.25399@reaper.quantumfyre.co.uk>
Le vendredi 27 mars 2009, Julian Phillips a écrit :
> On Fri, 27 Mar 2009, Christian Couder wrote:
> > If someone knows some other tools that can easily send a threaded patch
> > series, I will try to see if I can use them...
>
> I long ago gave up on send-email, as it seemed to cumbersome for what I
> wanted, and my perl had got so rusty I really couldn't face trying to
> improve it.
>
> So I wrote a replacement in Python (attached), which I have subsequently
> used for all patches I've sent. It calls format-patch, passing through
> arguments (and you can use -- to let it pass options too).
>
> (the only setting it reads from git config atm is mail-commit.to)
>
> I find it much easier to use than send-email, but as usual YMMV ...
Thanks I will try to have a look at it,
Christian.
next prev parent reply other threads:[~2009-03-27 7:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 4:55 [PATCH 01/10] refs: add "for_each_bisect_ref" function Christian Couder
2009-03-26 6:20 ` Sverre Rabbelier
2009-03-26 7:48 ` Christian Couder
2009-03-26 12:37 ` Sverre Rabbelier
2009-03-26 15:50 ` Michael J Gruber
2009-03-26 16:52 ` Johannes Schindelin
2009-03-26 16:54 ` Sverre Rabbelier
2009-03-27 0:41 ` Christian Couder
2009-03-27 1:32 ` sending patch sets (was: Re: [PATCH 01/10] refs: add "for_each_bisect_ref" function) Julian Phillips
2009-03-27 7:22 ` Christian Couder [this message]
2009-03-27 2:08 ` [PATCH 01/10] refs: add "for_each_bisect_ref" function Johannes Schindelin
2009-03-27 7:21 ` Christian Couder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903270822.01209.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johnflux@gmail.com \
--cc=julian@quantumfyre.co.uk \
--cc=srabbelier@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).