Karl,
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.)
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).
Unfortunately I don't have anywhere enough bandwidth to volunteer to help
out, but maybe next year if it's still outstanding (but I sincerely hope
it's not).
Anyway, thanks for taking the trouble to answer my posting.
Martin
On 8/7/06, Karl Fogel <kfogel@google.com> wrote:
>
> "martin budden" <mjbudden@gmail.com> writes:
> > I'd like to state that I'd really like to see the storage of text bases
> made
> > optional. In particular I'd like to see the following three
> user-configurable
> > options offered:
> >
> > a) text bases as they are (ie no change)
> > b) no text bases
> > c) no text bases, but hash of the file stored in .svn directory - this
> would
> > allow you to see that a file has been changed, although you wouldn't be
> able to
> > do diffs.
>
> Note that we store a hash of the text-base already (see the
> .svn/entries file). It is a way to do corruption checks.
>
> For text-base-less working copies, we'd want to store a hash of the
> working file too. This gets tricky, because if someone changes the
> svn:keywords or svn:eol-style property, the working file can change
> without it being "modified" in the sense that we usually mean by that
> word. Not an impossible problem, just a subtlety to watch out for.
>
> There is no reason to do (b) but not (c). If we allow text-base-less
> working copies, we should unconditionally keep a working file checksum
> and use it to detect when the file has been modified.
>
> Totally agree that solving #525 would be a Good Thing, by the way! :-)
>
> -Karl
>
Received on Tue Aug 8 19:18:29 2006