[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:09:06 CET

On Nov 29, 2007 7:04 PM, C. Michael Pilato <cmpilato@collab.net> wrote:
> David Glasser wrote:
> > * We disable "log -g" for 1.5. "log -g" was originally proposed as a
> > 1.6 command; it only switched to 1.5 because Hyrum finished his
> > implementation. (And there are a lot of good things about log -g; I
> > certainly have respect for Hyrum's work, and expect that 1.6 could
> > contain a fixed version of it.) This would allow us to ignore the
> > "log -g" bugs for now and focus on bugs more central to merge
> > tracking as opposed to just this one auditing feature
> >
> > * Because we no longer need it, we remove the sqlite mergeinfo index
> > from 1.5. This reduces a huge amount of code complexity in the FS
> > backends, and lets us not worry about fixing the bugs in keeping the
> > indices up to date. Because we don't need it, we don't use my
> > extra-metadata-in-DAG thing either.
> Are you saying that you think adding the extra-metadata-in-DAG is a bad idea
> right now? And am I reading correctly that if we *had* that today, we could
> still release 1.5 without the sqlite mergeinfo index and with 'svn log -g'
> support?

I am saying that the results I've seen from the extra error checking
that my metadata implementation does leaves me scared that "log -g"
has a longer way to go than we realized, and that I'd rather fix that
after 1.6 instead of before. (The extra error checking is also
revealing issues with more core merge-tracking features as well; I'd
rather be spending the time on those...)


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:09:16 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.