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

Re: [TSVN] Re: subwcrev suggestion: detect mixed working copy

From: Simon Large <slarge_at_blazepoint.co.uk>
Date: 2005-03-16 15:28:22 CET

Norbert Unterberg wrote:
> Let me rephrase my suggestion: It would be nice if subwcrev would
> detect that the working copy is not up-to-date. We want to detect
> that the currently compiled version might not be reproducable by a
> single checkout command because it contains files from different
> repository revisions.

Assuming we can easily read update revision rather than last-committed
revision, then we could use a $RevRange$ keyword and replace it with an
expression like 2780:2792. I will have a look when I have time.

>> if you modify some files and commit them, then those files have a
>> higher revision assigned to them (in the working copy) than the rest
>> of the working copy.
>
> As I understand the Subversion documentation, this is exactly the
> definition of "mixed revision working copy".

This is probably due to me hoping to detect svn up -rXXX file which
produces an out-of-sync working copy. It seems it is not possible to
distinguish whether a file is the wrong revision because I asked for
that revision, or just because it has not been updated.

Simon

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Mar 16 15:31:56 2005

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

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