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

Re: Copying commited WC

From: Nick Patavalis <npat_at_efault.net>
Date: 2005-01-05 22:03:50 CET

On 2005-01-05, Scott Palmer <scott.palmer@2connected.org> wrote:
>
> On Jan 5, 2005, at 1:43 PM, Nick Patavalis wrote:
>
>> Either "svn up" is "trivial" and nothing changes in
>> my WC, or "svn up" is not trivial, and there are other "side
>> effects" appart from making the WC single-revision. How can I tell
>> what will happen without actually issuing the update command?
>> Doing an "svn status" and examining the output seems to do the
>> trick; but unfortunately, status is checked against the tip of the
>> repo, not against a specific rMAX revision, which is what I want.
>>
>
> You can get the information from "svn diff -r MAX"

I guess you mean something like this:

  q=$(svn diff -r $rMAX 2>/dev/null | wc -l)
  if [ "$q" -ne 0 ]; then
      echo "WC cannot be made single-revision with a trivial update"
  else
      echo "WC can be made single-revision with a trivial update"
  fi

Right?

If so, then, I'm afraid it won't work. The "svn diff" command will
also ouput the *local modifications* made on the working copy. Because
of this any locally modified WC will be reported as one that can not
be trivially made single-revision; which is wrong.

/npat

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 5 22:06:26 2005

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