From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200101040031.AAA11766@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rev control 
In-reply-to: Your message of "Tue, 02 Jan 2001 20:31:01 PST."
             <20010103043102.9EDED199DD@mail.cse.psu.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
From: Steve Kilbane <steve@whitecrow.demon.co.uk>
Date: Thu,  4 Jan 2001 00:31:00 +0000
Topicbox-Message-UUID: 4331071c-eac9-11e9-9e20-41e7f4b1d025

jim:
> 	people do make sure things compile, but don't necessarily make
> 	sure things work
> 
> 	CVS diff is helpful, but it's still a pain in the ass to deal with merges
> 
> 	comments logged for commited code changes are useless one-liners like
> 	"changed stuff in function x" or "added feature y"
> 
> 	differences in coding style makes sharing a tree a pain in the ass
> 	when it comes to doing the aforementioned diff.

Well, sure, but this is just people being people (i.e. lazy). CVS is
a tool; it doesn't stop you screwing things up if you want. By and large,
you've also mentioned things that Plan 9 won't help with:

- people don't make sure things work. Well...

- merging sources is a pain; Plan 9 doesn't help with this, if you happen to
  be maintaining and merging multiple versions (e.g. development, release and
  historical versions of a product).

- the need for change logs are a function of the size of a project and the
  awareness of each programmer wrt the whole project. If you need 'em, you
  need 'em. Plan 9, of itself, doesn't help.

- if everyone's playing with their own coding style, then yes, it's going to
  be a pain merging. As long as you *are* merging, that is.

steve