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

Re: A little help needed when merging from non existant branches :)

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-12-06 19:23:08 CET

Lübbe Onken wrote:
> Hi Folks,
>
> Use case: Merge changes from a developer branch that doesn't exist anymore
> in HEAD into trunk.
>
> - Fire up the merge dialog
> - Remember that the branch doesn't exist anymore and open the repository
> browser from the merge dialog
> - Show log on repository root to find the revision number in which the
> branch was deleted
> - Manually set the revision number of the repo browser to this revision
> - Try to select a revision range from the log in the repo browser, hoping
> that this range will be transferred into the merge dialog
> - Close repo browser -> no revision range in merge dialog -> be unhappy
> - Notice that the manually set revision & branch URL have been copied into
> Start URL and revision -> be happy again
> - Click on show log (start revision) to select the revisions to merge from
> the log
> - Get an error message that the "Path does not exist". The revision number
> shown in the error is the HEAD revision.
>
> I would have expected TortoiseSVN to look at that branch with the given
> revision number and not at the HEAD revision.
>
> In short: "How can I get a log for a no more existing branch from the merge
> dialog?"

Use a nightly build later than revision 8245 :-)

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Dec 6 19:23:22 2006

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

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