From: Boyd Roberts <boyd@strakt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /n/dump vs CVS -- no contest: was: lucio-
Date: Thu, 10 Jan 2002 16:44:40 +0100 [thread overview]
Message-ID: <3C3DB6E8.66BBC362@strakt.com> (raw)
In-Reply-To: <20020110153138.58E7719A0B@mail.cse.psu.edu>
rob pike wrote:
> makes comparing CVS to /n/dump a dull exercise.
Yeah, with /n/dump and bind you can track down problems of the class:
hmm, looks like libc changed yesterday, so let's load with the
day before's and see if the bug goes away ...
prev parent reply other threads:[~2002-01-10 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 15:31 [9fans] lucio- rob pike
2002-01-10 15:44 ` Boyd Roberts [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=3C3DB6E8.66BBC362@strakt.com \
--to=boyd@strakt.com \
--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).