[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Projects?

From: Marc Singer <elf_at_buici.com>
Date: 2003-10-22 00:53:39 CEST

On Wed, Oct 22, 2003 at 12:34:14AM +0200, Robert Simmons wrote:
> > systems like Perforce that use a single repository wide changeset
> > number, and they seem to get by. What's the big issue you have with it?
>
> Every day some 10,000 people world wide get in their car and drive drunk. That
> doesnt mean its an especially good idea. Just because "others" do something
> doesnt mean I wish to do it as well. I simply dislike it when I have low change

I think I understand your point, though I would probably not have used
the example of drunk driving. Simply stated, driving drunk could not
be considered typical behavior for the general driving population.
Perforce, on the other hand, may be considered normative behavior for
many developers.

Yes, I agree that the repository-wide revision numbers require some
changes to our behavior as developers.

Yes, I agree that it is interesting and desirable to be able to ask
the question: how stable is this file or this set of files.

Speaking from the perspective of someone who has used CVS since the
mid-nineties, I think this is more about changing our behavior and
assumptions than about changing the tool.

Note that

  1) The revision number for a file only changes when the file changes
  2) A CVS-like revision number can be recovered from the log by
     counting the number of entries.
  3) Tagging is much more effective in subversion than CVS and should
     be used accordingly.

Cheers.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 22 00:54:23 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.