From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "John Goerzen" <jgoerzen@complete.org>, git@vger.kernel.org
Subject: Re: git-email automatic --to detection?
Date: Mon, 25 Feb 2008 19:26:18 +0030 [thread overview]
Message-ID: <4d8e3fd30802251056t626ff51dx8a6ea7a006222e72@mail.gmail.com> (raw)
In-Reply-To: <20080225183547.GB15131@sigill.intra.peff.net>
On 2/25/08, Jeff King <peff@peff.net> wrote:
> On Mon, Feb 25, 2008 at 02:26:03AM +0330, Paolo Ciarrocchi wrote:
>
> > I can't think of how to unify the commands from the ui point of view.
> > What do you suggest?
> >
> > However, i like the idea of a --send commad line option to
> > git-format-patch that calls git-send-email to create and send the
> > patch series.
>
> I think it makes sense the other way around: have git-send-email invoke
> git-format-patch.
>
> My reasoning is that git-send-email users almost always use
> git-format-patch, but git-format-patch users frequently do not use
> git-send-email.
that's correct. I even like the idea of a single git email command.
ciao,
--
Paolo
http://paolo.ciarrocchi.googlepages.com/
next prev parent reply other threads:[~2008-02-25 18:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 22:29 git-email automatic --to detection? John Goerzen
2008-02-24 22:56 ` Paolo Ciarrocchi
2008-02-25 15:07 ` John Goerzen
2008-02-25 18:35 ` Jeff King
2008-02-25 18:56 ` Paolo Ciarrocchi [this message]
2008-02-25 14:39 ` Miklos Vajna
2008-02-25 15:08 ` John Goerzen
2008-02-25 20:50 ` Miklos Vajna
2008-02-25 18:34 ` Jeff King
2008-02-25 18:57 ` Matthieu Moy
2008-02-25 19:19 ` Jeff King
2008-02-25 20:02 ` John Goerzen
2008-02-26 9:23 ` Matthieu Moy
2008-02-26 14:07 ` John Goerzen
2008-02-25 20:55 ` Miklos Vajna
2008-02-26 13:59 ` John Goerzen
2008-02-26 17:44 ` Miklos Vajna
2008-02-25 19:47 ` 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=4d8e3fd30802251056t626ff51dx8a6ea7a006222e72@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=git@vger.kernel.org \
--cc=jgoerzen@complete.org \
--cc=peff@peff.net \
/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).