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

Re: Up-to-date-check on commit.

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2002-06-20 04:52:30 CEST

On Thu, Jun 20, 2002 at 12:49:54AM +0200, Branko Čibej wrote:
> Josef Wolf wrote:
>
> >I am using CVS for 10 years now. Because of that I know that some
> >aspects of it are error prone. In real world errors happen when you
> >are in a hurry.
> >
>
> I understand your point, but the fact is that _no_ tool can help you
> avoid the problems caused by bad management. For example, even if
> Subversion warned Joe about Bob's changes, it won't stop Sam from
> picking up a snapshot before Joe's commit. Yes, the tarball will
> compile, but Joe's bugfix won't be in it.
>
As a concrete example, take subversion itself. I often commit with an out of
date tree (well of the times I commit), because I only update once per day
most of the time. I don't worry about it though, since I have seen the svn
commit emails, and can verify with them that no one else has been working on
the same files. I don't want to have to pass --force every time I commit.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  • application/pgp-signature attachment: stored
Received on Thu Jun 20 04:54:59 2002

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.