From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] Changed all (but one) occurrences of redwood to sup.
Date: Sat, 16 Feb 2008 11:13:47 -0800 [thread overview]
Message-ID: <1203188677-sup-4093@south> (raw)
In-Reply-To: <1202839827-11975-1-git-send-email-johannes@antiklimax.com>
Hi Johannes,
Reformatted excerpts from Johannes Martinsson's message of 2008-02-12:
> * Changed all occurrences of redwood to sup, but left out the one in the
> FAQ (What are all these "Red...).
Thanks for this very thorough patch. I'm going to hold off on applying
it until there's a good time with minimal changes (maybe when things
have synced up on a release) so as to avoid unnecessary conflicts.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-02-16 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 18:10 Johannes Martinsson
2008-02-16 19:13 ` William Morgan [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=1203188677-sup-4093@south \
--to=wmorgan-sup@masanjin.net \
/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