From: Steve Kilbane <steve@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rev control
Date: Thu, 4 Jan 2001 00:23:07 +0000 [thread overview]
Message-ID: <200101040023.AAA11532@whitecrow.demon.co.uk> (raw)
In-Reply-To: Your message of "Tue, 02 Jan 2001 22:54:16 EST." <20010103035425.D50F1199E6@mail.cse.psu.edu>
I was thinking about the CVS issue earlier today, and I couldn't see
any problems normally "solved" by CVS and its ilk that couldn't be
addressed by Plan 9's inherent facilities, and a little scripting
(compared to a lot of scripting for a UNIX system without a version
control system).
Obviously, yesterday is the heart of things. Equally important is
the namespace; multiple views through a global set of files is
the norm, not a special feature.
Tagging could be as simple as doing a find of a tree, and saving
the result in a file named after the tag.
The biggest gap appears to be a change log for commentary. Even
there, Plan 9's append-only file permissions reduce the need for
something complex down to "cat".
I'm not saying that it all becomes trivial; any large and/or complex
project tends to bite you in ways you didn't expect. I do think that
Plan 9 is a better place to start from, though.
Having said all that, I wonder whether there isn't a system in place
already because of the way Plan 9 itself has been developed. presotto
mentions a large project where no two versions ran the same code.
In constrast, almost all of Plan 9 is single-source. I suspect this
has been highly significant in the level of perceived need for a
management system.
steve
next prev parent reply other threads:[~2001-01-04 0:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 3:54 presotto
2001-01-03 4:28 ` James A. Robinson
2001-01-03 4:31 ` James A. Robinson
2001-01-03 4:31 ` James A. Robinson
2001-01-04 0:31 ` Steve Kilbane
2001-01-04 0:23 ` Steve Kilbane [this message]
2001-01-04 11:15 ` Boyd Roberts
2001-01-04 11:16 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-01-03 2:50 Russ Cox
[not found] <gja@meowing.net>
2001-01-02 17:47 ` greg andruk
2001-01-02 19:30 ` William K. Josephson
2001-01-03 1:33 ` Scott Schwartz
2001-01-04 5:12 ` greg andruk
2001-01-04 10:53 ` Boyd Roberts
[not found] <jim.robinson@Stanford.EDU>
2000-08-20 5:58 ` [9fans] booting problems with 3rd ed James A. Robinson
2000-08-22 0:04 ` James A. Robinson
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=200101040023.AAA11532@whitecrow.demon.co.uk \
--to=steve@whitecrow.demon.co.uk \
--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).