[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: Branko Čibej <brane_at_xbc.nu>
Date: 2002-06-20 09:38:37 CEST

Peter Davis wrote:

>On Wednesday 19 June 2002 19:52, Kevin Pilch-Bisson wrote:
>
>
>>I don't want to have to pass --force every time I commit.
>>
>>
>
>The innocent bystander (me) agrees with what a lot of people are saying here.
>Having to pass --force or any other option every time would be a terrible
>pain (I'm hardly ever at HEAD, especially when working on branches), but it
>would also be nice to have a little reminder that I am in fact not at HEAD.
>
>So I propose a compromise: check up-to-dateness for each commit, but make it
>only a WARNING condition if the check fails.
>
What's wrong with "svn st -u"? It tells you exactly what you want to
know. And we do write the number of the new HEAD revision on commit,
which you can check, too.

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 20 09:39:10 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.