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

Re: Comments on Issue #525 and Issue #908:Optional or compressed text base storage

From: Karl Fogel <kfogel_at_google.com>
Date: 2006-08-08 23:20:00 CEST

"martin budden" <mjbudden@gmail.com> writes:
> I guess the fact that you have answered my posting means that no-one
> is working on this and that you are following your rule of "reply to
> all postings". (I've just read "producing open source software",
> excellent book. A few colleagues at work joke that you could have
> called it "producing software" and 90% of it would have still
> applied.)

If only I were able to reply to all postings! :-)

I've heard recently that someone may be starting to work on optional
text bases. There have been false alarms on this before, so don't
jump for joy yet.

(Thanks for the nice mention of the book, too. I like to think it's
more about volunteer communities than about software per se, but that
may a fantasy.)

> Anyway, getting back on topic, I thought you might store a hash: I
> included it in my posting for completeness. The main reason for my
> posting was to add my voice to those asking for this feature, and to
> give a reason why non-existant textbases should be prioritised over
> compressed ones (though from the issue list #2539 needs to be done for
> both).

It's funny, it's one of those things that everyone agrees is important
(and I think most people agree that non-existent text bases are more
important than compressed text bases), but no one thinks it's
important enough to work on. It's not the easiest problem in
Subversion, but it's certainly not the hardest either. Someday,
someday...

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 8 23:20:43 2006

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.