From: Kirill Smelkov <kirr@landau.phys.spbu.ru>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: Kirill Smelkov <kirr@landau.phys.spbu.ru>,
Petr Baudis <pasky@suse.cz>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [TopGit RFC PATCH] tg mail: new command for mailing patches
Date: Fri, 19 Sep 2008 14:23:55 +0400 [thread overview]
Message-ID: <20080919102355.GG4423@roro3> (raw)
In-Reply-To: <36ca99e90809190320l4765e50eqe38bf1d2672cfcca@mail.gmail.com>
On Fri, Sep 19, 2008 at 12:20:49PM +0200, Bert Wesarg wrote:
> On Fri, Sep 19, 2008 at 12:04, Kirill Smelkov <kirr@landau.phys.spbu.ru> wrote:
> > On Fri, Sep 19, 2008 at 11:52:03AM +0200, Bert Wesarg wrote:
> >> On Fri, Sep 19, 2008 at 11:08, Kirill Smelkov <kirr@landau.phys.spbu.ru> wrote:
> >> > Petr, since you've asked for help on this, here you are:
> >> >
> >> > $ tg mail [NAME]
> >> >
> >> > a simple script to send one patch over email.
> >> >
> >> >
> >> > All it does is
> >> >
> >> > - call `tg patch` for actual patch preparation
> >> > - extract email addresses from whom and where to send a mail
> >> That shouldn't be needed. git send-email parses Cc: headers and the
> >
> > Exactly for this reason I do not extract Cc. And git send-mail does not
> > extract From: -- it just asks to confirm From is GIT_COMMITTER_IDENT,
> > and there is no option to stop it doing so except providing explicit
> > --from <someone> (maybe i'm missing something?).
> Ahh, my fault, I should take a break, sorry for the noise.
No problem, your "noise" is welcome :)
--
Всего хорошего, Кирилл.
prev parent reply other threads:[~2008-09-19 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 9:08 [TopGit RFC PATCH] tg mail: new command for mailing patches Kirill Smelkov
2008-09-19 9:52 ` Bert Wesarg
2008-09-19 10:04 ` Kirill Smelkov
2008-09-19 10:20 ` Bert Wesarg
2008-09-19 10:23 ` Kirill Smelkov [this message]
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=20080919102355.GG4423@roro3 \
--to=kirr@landau.phys.spbu.ru \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).