From: chrisw@rice.edu (Christopher Warrington)
Subject: [sup-talk] sup-announce?
Date: Sun, 19 Oct 2008 18:47:14 -0500 [thread overview]
Message-ID: <op.ujapo02csp4qz7@t-gewarr-tablet.ntdev.corp.microsoft.com> (raw)
In-Reply-To: <2d460de70810191641m2ed28e72q801429381ec66a89@mail.gmail.com>
Richard Hartmann <richih.mailinglist at gmail.com> @ 2008-10-19 06:41 PM
"Re: [sup-talk] sup-announce?"
<2d460de70810191641m2ed28e72q801429381ec66a89 at mail.gmail.com>
>> Feedback from others would be appreciated, yes :)
>
> Poke? :)
Sure, why not?
--
Christopher Warrington <chrisw at rice.edu>
Jones College
next prev parent reply other threads:[~2008-10-19 23:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 15:58 Richard Hartmann
2008-10-15 18:08 ` William Morgan
2008-10-15 23:49 ` Richard Hartmann
2008-10-19 23:41 ` Richard Hartmann
2008-10-19 23:47 ` Christopher Warrington [this message]
2008-10-20 2:42 ` William Morgan
2008-10-20 8:22 ` Richard Hartmann
2008-10-21 0:21 ` William Morgan
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=op.ujapo02csp4qz7@t-gewarr-tablet.ntdev.corp.microsoft.com \
--to=chrisw@rice.edu \
/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