From: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
To: git@vger.kernel.org
Subject: Re: [PATCH 0/2] Assist installing documentation with incomplete build chain
Date: Wed, 10 Sep 2008 11:16:53 +0200 [thread overview]
Message-ID: <48C79085.6090005@fastmail.fm> (raw)
In-Reply-To: <cover.1221035620.git.michaeljgruber+gmane@fastmail.fm>
I hate to reply to myself, but I apologize for the failed threading.
That series has Message-Id: and In-Reply-To: fields set up
appropriately, but it doesn't show up threaded, at least not here. It
was an attempt at using Thunderbird, by writing format-patch output to
TB's outbox in mbox format (and adding a few lines). I'll try
differently next time (the approach with external editor + TB-config
changes isn't that comfortable either).
Michael
prev parent reply other threads:[~2008-09-10 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 8:33 [PATCH 0/2] Assist installing documentation with incomplete build chain Michael J Gruber
2008-09-09 20:44 ` [PATCH 1/2] allow installation of man and html doc from the man and html branches Michael J Gruber
2008-09-10 8:19 ` [PATCH 2/2] separate build targets for man and html documentation Michael J Gruber
2008-09-10 9:16 ` Michael J Gruber [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=48C79085.6090005@fastmail.fm \
--to=michaeljgruber+gmane@fastmail.fm \
--cc=git@vger.kernel.org \
/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).