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

Re: A modest proposal: No index or "log -g" in Subversion 1.5

From: David Glasser <glasser_at_davidglasser.net>
Date: 2007-11-30 04:13:25 CET

On Nov 29, 2007 7:07 PM, Ben Collins-Sussman <sussman@red-bean.com> wrote:
> I'm going to have a really hard time saying to people, "Oh hey, you
> can now repeatedly merge trunk to your branch now without tracking
> revisions manually. But, um, when you merge back, you better get the
> -rX:Y argument just right." It doesn't feel like very much progress.
> I define "success" as "the user never needs to type a revnum".

Is svnmerge.py any better than this here? (I don't know.)

I also do think that the -rX:Y argument can be automatically
calculated; it just uses a different mechanism than svn:mergeinfo.

> What I'd like to understand is: how does this new sqlite-less design
> (which sounds great!) actually relate to the various solutions we've
> discussed for issue 2897? Is sqlite really required to subtract one
> patch from another patch?

I'm not positive. I still don't have a full understanding of what
sorts of queries solving Issue 2897 in the ways we are currently
proposing requires. (But I do think that whatever information is
necessary, maintaining it accurately seems to require simulating the
Subversion DAG explicitly or implicitly, which is not exactly


David Glasser | glasser_at_davidglasser.net | http://www.davidglasser.net/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 30 04:13:37 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.