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

Re: Merge tracking proposal, rev 2

From: John Peacock <jpeacock_at_rowman.com>
Date: 2006-05-10 02:33:58 CEST

Daniel Berlin wrote:
> solo turn wrote:
>> as the only possibility to solve that problem up to now was svk, and i
>> guess many people know svk: what is the difference between svk and
>> your proposal?
> In terms of what?
> My proposal is simply a design for storing the merge information.
> Nothing more, nothing less.

I was also wondering how your proposal differs from how SVK is currently storing
merge information. I realize that your proposal doesn't include SVK's multiple
merge methodologies (star-merge, cherry-picking, and, just recently added to
trunk, interactive commit). But there are already merge tags in Subversion's
own repository that originate from SVK commits. How are those tags going to
interoperate with your proposed tags? What feature of your proposal is superior
to the existing scheme that SVK has been sucessfully employing for several years


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 10 02:34:13 2006

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