From: "\"Nils O. Selåsdal\"" <NOS@Utel.no>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] patch auto-mails
Date: Thu, 8 Sep 2005 07:32:39 +0200 [thread overview]
Message-ID: <431FCCF7.3080604@Utel.no> (raw)
In-Reply-To: <000001c5b3ef$43a85c70$14aaa8c0@utelsystems.local>
David Leimbach wrote:
> I actually didn't mind these emails. It was neat to see what was
> going on there :).
I agree, as long as the list isn't flooded with these, it's ok -
and a nice way to follow the changes.
prev parent reply other threads:[~2005-09-08 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 15:15 [9fans] [patch] sorry: vncconnect patch-log
2005-09-07 15:19 ` [9fans] patch auto-mails Russ Cox
2005-09-07 20:48 ` David Leimbach
2005-09-07 22:22 ` LiteStar numnums
2005-09-08 3:33 ` [9fans] " Russ Cox
2005-09-08 23:17 ` David Leimbach
[not found] ` <000001c5b3ef$43a85c70$14aaa8c0@utelsystems.local>
2005-09-08 5:32 ` "Nils O. Selåsdal" [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=431FCCF7.3080604@Utel.no \
--to=nos@utel.no \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).