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

Re: branching and switch question

From: William Nagel <bill_at_stagelogic.com>
Date: 2004-08-25 18:14:07 CEST

Hash: SHA1

If you run 'status -v' it will show you the current revision of each
file in your working directory (recursively). You can use this as a
quick sanity check before doing the branch, in order to ensure that
you're getting the correct revision.

- -Bill

On Aug 25, 2004, at 10:55 AM, Fery wrote:

> William Nagel wrote:
>> Could you post the exact commands you're running, along with the
>> result
>> of 'svn status -uv' and 'svn info' in your current working directory?
> Sorry, I was typing faster than thinking. Meanwhile I have found the
> problem: it was that 'svn info' gives misleading information:
> ...
> Revision: 150
> ...
> Last Changed Rev: 150
> ...
> Based on that, I have created the branch from revision 150.
> The problem is, that these numbers do not get updated when I commit a
> new revision. I.e., in the example above, it happened that my base
> actually was 152, where I have committed the 151 and 152. So, after
> that
> when I tried to switch, then it tried to undo these two revisions,
> which
> conflicted with my actual modifications.
> To prevent this type of error, I should execute 'svn update' after
> every
> 'svn commit'. But it would really help if svn info would warn me if
> there are files with recent versions in the directory (recursively)
> than
> the directory itself.
> Thanks,
> Ferenc

Version: GnuPG v1.2.4 (Darwin)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 25 18:15:09 2004

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

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