From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Teach the --cover-letter option to format-patch
Date: Tue, 10 Jul 2007 18:20:35 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707101819350.4047@racer.site> (raw)
In-Reply-To: <Pine.LNX.4.64.0707101300450.6977@iabervon.org>
Hi,
On Tue, 10 Jul 2007, Daniel Barkalow wrote:
> I think this is missing the ultra-important "extra_headers" stuff, which
> is what makes my messages actually reach the right people. That's why
> I'd like the code shared for generating headers (except for Subject) for
> a rev_info between the code that does it for patch messages and the code
> for the cover letter. I think it's also missing making [PATCH 1/N] a
> reply to it if the series is set up as replies.
Ah yes. Both issues should be relatively easy to integrate into my patch.
> I like the design, in any case. I want the blurb actually stored in the
> objects directory somehow, so that I don't have to trawl through my sent
> email for it when I send the series again for some reason, but that's a
> relatively straightforward extension to your code. (Read an object with
> a hash and stick the text in instead of the ***...*** parts.)
I do not understand. But then, my patch should be a good starting point.
Go wild.
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-10 17:28 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
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 [this message]
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.0707101819350.4047@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).