From: erik quanstrom <quanstro@coraid.com>
To: akumar@mail.nanosouffle.net, 9fans@9fans.net
Subject: Re: [9fans] spreading the word
Date: Mon, 23 Feb 2009 18:46:02 -0500 [thread overview]
Message-ID: <e0c3d04b3b83edb33481a8c935fe7d27@coraid.com> (raw)
In-Reply-To: <b2156092068cd73e082f23236ad92084@mail.nanosouffle.net>
> No discussion involving Einstein and Ken should have spelling mistakes
> in the topic.
>
> It complicates the understanding
as does changing the Subject: .
there are always tradeoffs.
- erik
prev parent reply other threads:[~2009-02-23 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 23:39 Akshat Kumar
2009-02-23 23:46 ` erik quanstrom [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=e0c3d04b3b83edb33481a8c935fe7d27@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@9fans.net \
--cc=akumar@mail.nanosouffle.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;
as well as URLs for NNTP newsgroup(s).