From: merlyn@stonehenge.com (Randal L. Schwartz)
To: git@vger.kernel.org
Subject: Re: [BUG] making docs blows up in b1bfcae438ad:git-merge-file.txt
Date: 17 Dec 2006 10:20:33 -0800 [thread overview]
Message-ID: <86ac1mcrke.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20061216234717.15ECE8F5A8@blue.stonehenge.com>
>>>>> "The" == The Answering Machine <merlyn.'s-answering.machine@stonehenge.com> writes:
The> I've received your mail.
The> Your message has been queued, and will probably be read within 48 hours.
Naughty SCM sent email addressed to me personally, but added a reply-to
of the list.
My answering machine behaved perfectly in this case, but SCM triggered it
badly. :(
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
next prev parent reply other threads:[~2006-12-17 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 23:41 [BUG] making docs blows up in b1bfcae438ad:git-merge-file.txt Randal L. Schwartz
2006-12-16 23:47 ` A Large Angry SCM
2006-12-16 23:47 ` The Answering Machine
2006-12-17 18:20 ` Randal L. Schwartz [this message]
2006-12-17 14:48 ` [PATCH] Documentation/git-merge-file.txt: make asciidoc not complain Johannes Schindelin
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=86ac1mcrke.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--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