On 2005-01-05, Ben Collins-Sussman <sussman@collab.net> wrote:
>
> On Jan 5, 2005, at 11:45 AM, Steve Greenland wrote:
>> My point was that for ex-CVS
>> users, the whole concept of a commit causing the WC to be "out-of-date"
>> is, let us say, unusual. From the SVN "repository versions, not file
>> versions" point-of-view, it's consistent, if not always convenient.
>>
>
> Yep, versioning directories means that CVS users have to occasionally
> do a of paradigm-tweakage in their heads. ;-)
Yes, I can also understand this. Two are my problems, though:
- Copying a mixed-revision WC seems not to work. As you say, though,
this is a bug; right?
- I have a mixed-revision WC with base-revisions from rMIN to
rMAX. It is possible (though not certain) that this WC corresponds
to an *identical* single-revision WC. If so, I want to convert my
mixed WC to a single-revision one. If I do an "svn up -r rMAX"
then the WC will indeed become single-revision, but there are two
possibilities: 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.
/npat
P.S. I'm using subversion 1.0.9 (r11378), compiled Oct 16 2004,
23:29:24. It is the latest packaged version that comes with
Debian Sarge; namely debian-package version 1.0.9-2
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 5 19:47:54 2005