From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in read(1)
Date: Wed, 22 May 2002 00:30:57 -0700 [thread overview]
Message-ID: <200205220730.g4M7Uv5u026480@ducky.net> (raw)
In-Reply-To: <56143d25fd265eed76f8e8a6c4968f55@plan9.bell-labs.com>
>I put a fixed version on sources.cs.bell-labs.com.
Wow, the new distribution system is less than 12 hours old
and already I am approximately 1E6 times as happy with it
as I was with ad-hoc emailed patches. Only about 1 hour
elapsed from bug report to bug fix downloaded with no manual
merging or fear of forgetting local changes.
next prev parent reply other threads:[~2002-05-22 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 6:14 rob pike, esq.
2002-05-22 7:30 ` Mike Haertel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-22 5:54 Mike Haertel
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=200205220730.g4M7Uv5u026480@ducky.net \
--to=mike@ducky.net \
--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).