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

[TSVN] stupid user (me!) - switch auto-updated repository - should it have?

From: Alan Jay Weiner <alan_at_ajw.com>
Date: 2004-11-02 17:32:09 CET

Uh, first, I'm still on the older version - need to back things up and move to
latest and greatest... I'm on Subversion 1.0.5 (or 1.0.6?) and TSVN 1.0.8
(and I promise to update to latest today! :)

But I'm guessing that what I did is normal behavior (and still will occur with
latest) so I'm confused - seems like the repository was changed ("committed")
when I wasn't expecting it to - and **without changing the revision number**.
So I'm asking for clarification - what did I do wrong?

What I did was made a copy of foo/trunk (HEAD) to foo/branches/workonsomething

No problem - created the branch fine:
        foo/trunk is revision 326
        foo/branches/workonsomething is revision 328
        (327 is on another project, btw)

I'd already made lots of changes in my working copy; they're buggy, so I wanted
to change so I'm working on a branch.
Working copy was originally same as foo/trunk (HEAD).

So I right-clicked in my working copy and used TSVN's "Switch" (my first
mistake? should I have "relocated"?) and selected the branch:
         foo/branches/workonsomething

Got a dialog with a list of changes (update, conflict, etc - but dismissed it
too quickly so can't refer to it now). I *thought* it was informational -
what's different between the branch and my working copy.

Instead it appears to have automagically changed the branch to look like my
working copy - without a new revision number! The only thing not in the
repository is a couple of new files.
(I checked out a new copy of branch and diff'd - it's really changed)

Now I'm confused -

should I have done a relocate instead of a switch? I took relocate to mean
switching the repository location; does it work to switch the working copy's
"baseline" from one revision to another?

Why did the switch update the repository? I'm *very* thankful I didn't lose my
changes, but I didn't expect it to automatically commit my changes, and without
a chance for me to add a comment - and worse, without changing the revision
number! (I wonder - would I hose the trunk HEAD if I switch back to it!?!?)

foo/trunk is still revision 326 (as expected)
foo/branches/workonsomething is still revision 328 - why isn't it 329 with 328
being the "cheap copy" of revision 326 and 329 being my changes?

Ok, explanation, please! (and I'm off to go update SVN and TSVN :)

- Al -

-- 
--  Alan Weiner  --  alan_at_ajw.com  --  http://www.ajw.com
Palm OS Certified Developer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Nov 2 17:33:32 2004

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