From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Some comments on sup-0.6
Date: Sun, 24 Aug 2008 17:01:51 -0700 [thread overview]
Message-ID: <1219622436-sup-327@entry> (raw)
In-Reply-To: <6bb609560808231657m27ec05fq3418cc9ad5f4eb27@mail.gmail.com>
Reformatted excerpts from barton.schaefer's message of 2008-08-23:
> Those blog posts are from a couple of months ago. I could go comment
> there, or I could comment here. Any preference?
Here's probably better for anything substantial. Non-threaded blog
comments are about as crappy a discussion medium as I can imagine.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-08-25 0:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 23:15 Bart Schaefer
2008-08-23 23:20 ` Luis Villa
2008-08-23 23:57 ` Bart Schaefer
2008-08-25 0:01 ` William Morgan [this message]
2008-08-25 0:30 ` William Morgan
2008-08-25 16:39 ` Bart Schaefer
2008-08-25 20:55 ` Marcus Williams
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=1219622436-sup-327@entry \
--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