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

Re: export, checkout, commit performance

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2006-03-18 14:10:38 CET

On Fri, Mar 17, 2006 at 11:16:19PM +0100, Peter N. Lundblad wrote:
> Malcolm Rowe writes:
> > This is r4374, yes? I know that wc's are long-lived, but do we _really_
> > need to be able to read wc's that haven't been updated in the last
> > three years, since 0.17.x? (Or am I wrong in thinking we'll rewrite
> > the checksum whenever we rewrite the entries file?)
> >
> Well, since the function we're talking about requires a write lock,
> and that will have upgraded the WC to format version 6, which in turn
> will have rewritten the entries file, I conclude that you're right.
> Dropping that compat hack now.

Even better! Looking around for any other evidence of the old behaviour,
I see that (struct svn_wc_entry_t).checksum is currently documented as:

  /** base64-encoded checksum for the untranslated text base file,
   * can be @c NULL for backwards compatibility.
  const char *checksum;

(in include/svn_wc.h).

I presume that's wrong, but I don't know what the best way to describe
the checksum is - 'ASCII-encoded MD5 checksum'? Not very clear, imo.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 18 14:11:07 2006

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