From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Theodore Tso <tytso@mit.edu>
Cc: Junio C Hamano <gitster@pobox.com>,
Daniel Barkalow <barkalow@iabervon.org>,
git@vger.kernel.org
Subject: Re: [RFC] series headers
Date: Tue, 10 Jul 2007 16:23:09 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707101617520.4047@racer.site> (raw)
In-Reply-To: <20070710144808.GA27033@thunk.org>
Hi,
On Tue, 10 Jul 2007, Theodore Tso wrote:
> On Tue, Jul 10, 2007 at 02:56:48PM +0100, Johannes Schindelin wrote:
> > And what is so wrong with
> >
> > [insert before format-patch] $EDITOR my-cover-letter.txt
> >
> > [replace $EDITOR 0000-cover-letter.txt] $EDITOR my-cover-letter.txt
> > 0000-cover-letter.patch
> >
> > and paste the changed text?
>
> Nothing is *wrong* with it per-se, but if you have multiple things that
> you are working on at the same-time, you might not want to keep
> 0000-cover-letter.patch in your working directory.
Ah, but then maybe you want to be able to say
git format-patch --cover-letter=<my-cover-letter> [...]
Where your cover-letter file looks something like this:
My patch series which will rule the world
Here is the body, and I explain what the world should look like,
and that they should accept me as the chosen one president of the
united geekheads of this world.
IOW the file contents to produce what is produced with my patch would look
like this:
*** SUBJECT HERE ***
*** BLURB HERE ***
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-10 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 6:14 [RFC] series headers Daniel Barkalow
2007-07-10 6:57 ` Junio C Hamano
2007-07-10 13:24 ` Theodore Tso
2007-07-10 13:56 ` Johannes Schindelin
2007-07-10 14:48 ` Theodore Tso
2007-07-10 15:23 ` Johannes Schindelin [this message]
2007-07-10 13:26 ` [PATCH] Teach the --cover-letter option to format-patch Johannes Schindelin
2007-07-10 17:20 ` Daniel Barkalow
2007-07-10 17:20 ` Johannes Schindelin
2007-07-24 20:12 ` Peter Oberndorfer
2007-07-24 20:19 ` Daniel Barkalow
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=Pine.LNX.4.64.0707101617520.4047@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tytso@mit.edu \
/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).