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

Re: Merge tracking

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-03-30 06:59:38 CEST

On Mar 26, 2005, at 12:45 AM, Carl Baldwin wrote:
>
> I am willing to put some time/effort toward this little piece. Before
> diving into it I would like to discuss with those who are interested
> exactly how this information will be recorded by the 'svn merge'
> command.
>

Hi Carl,

Glad you're interested in this task. You've not seen many responses
because most of us are busy trying to get a 1.2 release stable and out
the door. We've just spent months working on another 'huge' feature
(locking), and most of us don't have time/energy to start a bunch of
long design discussions for merge-tracking.

This discussion *will* happen... it's on our roadmap. I think you just
happened to choose a bad moment to try and attract attention.

Once svn 1.2 is out, the next thing we'd like to design is 'true
moves', because some of us feel that it's a prerequisite for
good-quality merge tracking.

Here's our rough roadmap:

    http://subversion.tigris.org/roadmap.html

And here are some preliminary thoughts on merge tracking:

    http://svn.collab.net/repos/svn/trunk/notes/merge-tracking.txt

I think you're already jumping the gun in trying to propose specific
types of merge-tracking properties. There's a much larger discussion
to be had first: what *is* merge-tracking? There seems to be a whole
class of problems by that name. We need to enumerate them, prioritize
them, etc.

Again, you're welcome to plow forward. But you might get more
attention if you wait a month. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 30 07:01:03 2005

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.