From: albert@users.sf.net (Albert Cahalan)
Subject: [TUHS] cvsweb for BSD
Date: 08 May 2004 12:15:20 -0400 [thread overview]
Message-ID: <1084032920.952.272.camel@cube> (raw)
In-Reply-To: <20040508171033.7962.qmail@web50605.mail.yahoo.com>
On Sat, 2004-05-08 at 13:10, Kenneth Stailey wrote:
> Possibly converting SCCS to RCS to CVS. I don't know how far back my BSD SCCS
> goes.
>
> Maybe a smaller project to CVS 4.3BSD-tahoe to Quasijarus first.
>
> One of the big problems is that they move files all over the place as BSD
> developed and CVS doen't work too elegantly with those kind of changes.
Bitkeeper handles this well. I suspect that Larry McVoy would
at least be mildly interested in giving advice for such
a project. Bitkeeper is SCCS-based.
Bitkeeper also has a superior web interface. You can't beat
standard unified diff format with a tiny bit of color added.
next prev parent reply other threads:[~2004-05-08 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 17:10 Kenneth Stailey
2004-05-08 16:15 ` Albert Cahalan [this message]
2004-05-08 19:19 ` M. Warner Losh
2004-05-08 22:07 ` Kenneth Stailey
2004-05-08 17:19 Michael Sokolov
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=1084032920.952.272.camel@cube \
--to=albert@users.sf.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;
as well as URLs for NNTP newsgroup(s).