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

Re: How to merge from URL@N?

From: Ryan J Ollos <ryano_at_physiosonics.com>
Date: Fri, 8 Jul 2011 23:45:41 -0700 (PDT)

Stefan Küng wrote:
> Try the next nightly build. I'll commit a change in a few minutes that
> allows to specify the peg revision in the revision range string at the
> end:
> 5-7,20-30,66-77_at_99
> the peg revision can be added at the end, indicated with an '@' char.
> The next nightly build will have this feature.
> Stefan

I've installed `TortoiseSVN 1.6.99, Build 21671 - 64 Bit -dev, 2011/07/08

The text below the `Revision range to merge` text box now shows that it is
possible to specify @pegrevision, but it doesn't seem to be working for me.

As a confirmation that we are merging from a peg revision, in the merge
dialog it would be helpful if the first line read:
Merging revisions N-M of URL_at_PEGREVISION into WC, respecting ancestry

whereas it currently reads:
Merging revisions N-M of URL into WC, respecting ancestry

A feature that might be user friendly would be:
 * User opens Repository Browser from the Merge dialog to select a URL.
 * User changes the Revision when browsing the repository and then selects a
 * In response to the user selecting a directory, TSVN populates the `URL to
merge from` text box. Perhaps TSVN should also populate the `Revision range
to merge` with @PEGREVISION as well.

Here is a screen capture to better show what I'm talking about:
http://old.nabble.com/file/p32026345/Merge.png Merge.png

View this message in context: http://old.nabble.com/How-to-merge-from-URL%40N--tp32019597p32026345.html
Sent from the tortoisesvn - users mailing list archive at Nabble.com.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-07-09 08:45:50 CEST

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.