Tobin Bergen-Hill wrote:
> Stefan Küng wrote:
>> Tobin Bergen-Hill wrote:
>>> The Specific Revision field of the Copy (Branch/Tag) dialog is empty by
>>> default. This option is useful for branching from the current
>>> checkout's revision (even if it is not the latest revision); however,
>>> the user has to manually determine the item's current revision (e.g.
>>> right-click the item, choose Properties, look at the Subversion tab) and
>>> manually enter it in the field. This should fill in with the selected
>>> item's revision in the current checkout by default, thus saving the user
>>> these manual steps.
>> That revision you see in the properties dialog is the last committed
>> revision of that file or folder. It is *not* the revision your working
>> copy is on. To determine that revision, you have to check that
>> revision of every file and folder in your working copy - and that can
>> really take some time if you have a big working copy. (Also, that's
>> what our SubWCRev tool is for).
> There are two fields displayed in the Subversion tab of the Properties
> dialog for a selected folder: the Revision/Author (which is the revision
> I'm looking for when branching) and the "Last commit revision" (which is
> what you're talking about). This is assuming that the developer has
> updated at the level of the selected folder and not at some subfolder.
> It seems like a safe assumption when a folder is selected - especially
> since this is a default value for that field and can be easily changed
> if wrong.
Why is that safe? If you commit a single file or a subfolder, the parent
folder will not be up-to-date. There is nothing visible to show you
that, and if you create your branch from there it will be missing those
In any case, if you are assuming that you have just updated, you could
branch from HEAD.
>> If you want to create a branch/tag from a specific revision, use the
>> log dialog and just select the revision you want - or use the
>> repository browser.
> The repository browser does not list any revisions not committed.
> That's why the developer must obtain the Revision/Author revision
> manually from the Properties tab - again, assuming that the developer
> has updated at the level of the selected folder.
Excuse me? What exactly is a revision not committed? Any revision which
appears in the revision/author field must be in the repository. If you
mean local changes then you need to branch from the working copy, not
from the repository.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Sep 9 18:56:35 2005