From: Jon Seymour <jon.seymour@gmail.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Linus Torvalds <torvalds@osdl.org>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH] Add script for patch submission via e-mail.
Date: Tue, 5 Jul 2005 19:39:10 +1000 [thread overview]
Message-ID: <2cfc40320507050239605e8d3a@mail.gmail.com> (raw)
In-Reply-To: <20050705093441.GD6191@pasky.ji.cz>
On 7/5/05, Petr Baudis <pasky@suse.cz> wrote:
>
> 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. ;-)
As one who inhabits that dark world, I second that!
jon.
next prev parent reply other threads:[~2005-07-05 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 1:32 [PATCH] Add script for patch submission via e-mail Junio C Hamano
2005-07-05 9:34 ` Petr Baudis
2005-07-05 9:39 ` Jon Seymour [this message]
2005-07-05 15:20 ` Junio C Hamano
2005-07-05 16:18 ` Jon Seymour
2005-07-05 20:19 ` Junio C Hamano
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=2cfc40320507050239605e8d3a@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=jon@blackcubes.dyndns.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
--cc=torvalds@osdl.org \
/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).