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

Re: merge tracking use cases

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2007-12-01 01:51:56 CET

On Nov 30, 2007 4:02 PM, Daniel Rall <dlr@collab.net> wrote:
> Ignoring some bugs in what we do have, what we don't support fully
> includes:
> - Merging
> - Block/Unblock Changeset

Not that I have much time right now to invest in this, but this lack
of block is going to make merge tracking very very annoying - probably
so much that I wouldn't even use merge tracking.

Perhaps the easy way out is to just have 'svn block -c xxxx' do a
record-only merge?

But, if a rev constantly appears in the avail list, that's gonna be
downright annoying - probably so much so that I'd stick with
svnmerge.py. The galling point is that I don't think I'm the only one
who uses block or expects it to be there.

(I frankly care more about block than I do about bi-directional
merges.) -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 1 01:52:06 2007

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

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