From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] CVS (Was: lucio-)
Date: Wed, 9 Jan 2002 13:26:22 +0200 [thread overview]
Message-ID: <20020109132621.O12098@cackle.proxima.alt.za> (raw)
In-Reply-To: <3C3C2265.5D8B1EFD@strakt.com>; from Boyd Roberts on Wed, Jan 09, 2002 at 11:58:45AM +0100
On Wed, Jan 09, 2002 at 11:58:45AM +0100, Boyd Roberts wrote:
>
> Lucio De Re wrote:
> > No offense meant, but doesn't this show precisely what CVS's strength
> > is? Had you recorded the fix, we wouldn't be still looking for it :-)
>
> Having used both, I'd go for /n/dump.
Just to change the Subject: :-)
On kfs?
++L
PS: I think /n/dump is a great idea, specially as it is automatic and
not subject to the vagaries of human fallibility. I can even accept
that its positive features far outweigh its coarse granularity and an
inability to mark files as members of revision sets. But if I had to
add features to /n/dump (which is not a trivial task in itself) I
would look to CVS for starting guidelines.
next prev parent reply other threads:[~2002-01-09 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 3:06 [9fans] lucio- Russ Cox
2002-01-09 4:49 ` Lucio De Re
2002-01-09 4:52 ` Lucio De Re
2002-01-09 10:58 ` Boyd Roberts
2002-01-09 11:26 ` Lucio De Re [this message]
2002-01-09 11:43 ` [9fans] CVS (Was: lucio-) Boyd Roberts
2002-01-09 12:02 ` Lucio De Re
2002-01-09 16:01 ` [9fans] lucio- Aharon Robbins
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=20020109132621.O12098@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).