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

Re: Default revision for branch/tag

From: David <dwhite_at_gbcsci.com>
Date: Thu, 25 Feb 2010 22:38:28 +0000 (UTC)

Stefan Küng <tortoisesvn@...> writes:

>
> On 25.02.2010 05:45, David wrote:
> > Hello,
> >
> > In the past the default revision when I tag a version is the HEAD revision,
> > but now it offers me version 2220. Of course I can switch it to HEAD, but
it
> > worries me that it doesn't default to that because I wonder if my working
> > directory is as it was at version 2220.
> >
> > I have done an Update to HEAD revision (no changes occurred) but it still
> > offers the same revision for tagging. Why is this, and is there a command
with
> > which I can set or check the current revision of my working directory?
>
> That's the better behavior: Imagine someone else does a commit while you
> have the branch/tag dialog open. You think you're tagging from HEAD
> which you *know*, but since someone else did a commit HEAD is not what
> you *know* anymore but only what you *think*.
> So HEAD has changed without you knowing about it yet.
> TSVN therefore helps you avoid such problems and offers you the revision
> your working copy is on as the default to tag from. Because that's the
> revision you think is HEAD (which is identical to HEAD if no one else
> did a commit in between).

Okay, that makes sense. Thanks. I updated my Tortoise version recently. Is
that likely to be the only reason for the change? I was concerned mainly
because it _used to_ offer HEAD and now it doesn't, but thinking back maybe
this occurred when I updated my Tortoise.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2452245

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-25 23:38:51 CET

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

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