From: Matt McCutchen <matt@mattmccutchen.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Sending a threaded patch series with Evolution
Date: Sat, 13 Dec 2008 21:34:18 -0500 [thread overview]
Message-ID: <1229222058.2838.22.camel@mattlaptop2.local> (raw)
In-Reply-To: <m3hc57g28b.fsf@localhost.localdomain>
On Sat, 2008-12-13 at 14:05 -0800, Jakub Narebski wrote:
> By the way, your message [PATCH 2/2] should be threaded, i.e. be
> response to [PATCH 1/2] (or to cover letter [PATCH 0/2]), to not
> mistake it with other [PATCH 2/2] patches.
I'm using Evolution 2.24 as my mail client, and I have a wrapper script
"git draft-patch" that runs "git format-patch" and loads the patches
into my Evolution Drafts folder so I can look them over in the composer
and add non-commit-message text below the "---" if I wish before
sending. I did pass --thread, but the composer changed the Message-Id,
breaking the threading.
I'll try to get this right in the future. I can see two approaches to
doing so:
1. Check over / edit the patches in a text editor before loading them
into Drafts, and then send them by moving them directly to Outbox
(without using the composer) so that the Message-Id won't change.
2. Send the first patch, then manually edit the Message-Id Evolution
assigned it into the second patch, etc.
Neither of these approaches is particularly nice. Does anyone have a
better idea?
--
Matt
next prev parent reply other threads:[~2008-12-14 2:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ba6b6c3fc183002407f322663d7ab53c1c28a91.1229202740.git.matt@mattmccutchen.net>
2008-12-13 21:16 ` [PATCH 2/2] gitweb: support hiding projects from user-visible lists Matt McCutchen
2008-12-13 22:02 ` Jakub Narebski
2008-12-13 22:05 ` Jakub Narebski
2008-12-14 2:34 ` Matt McCutchen [this message]
2008-12-24 1:40 ` Matt McCutchen
2009-01-02 19:33 ` Jakub Narebski
2009-01-03 18:29 ` gitweb config with some public, some basic-authenticated repos Matt McCutchen
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=1229222058.2838.22.camel@mattlaptop2.local \
--to=matt@mattmccutchen.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).