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

Fwd: Log message templates revisited.

From: Jim Blandy <jimb_at_red-bean.com>
Date: 2005-11-12 05:44:09 CET

[reply button klutz]

---------- Forwarded message ----------
From: Jim Blandy <jimb@red-bean.com>
Date: Nov 11, 2005 7:27 PM
Subject: Re: Log message templates revisited.
To: Daniel Berlin <dberlin@dberlin.org>

On 11/11/05, Daniel Berlin <dberlin@dberlin.org> wrote:
> > We could just always store all the properties of all a directory's
> > parents somewhere in its .svn subdir. (To keep wc directories
> > independent, we'd need to repeat it, even when the wc parent is based
> > on the repos parent.) Retch, but seriously, how much space are we
> > talking about here? And we know we want the facility.
>
> The problem with space usage on the client side isn't that we have
> properties at all, it's that we store file properties for a single
> file .... in a single file per file :)

Well, okay, hopefully we'll learn from our mistakes. :)

Perhaps we could have a selected list of properties to save
client-side, much like the selected list of properties whose presence
or absence we save. That way, we wouldn't suffer if someone decided
to set some huge property way up in the hierarchy. The offline access
wouldn't work for everything automatically, but it'd be easy to add it
when we discover someone cares about something. Or maybe a config
file entry listing parent properties to cache locally?

(I have zero clue how things are done client-side, which is why I'm
being so vague.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 12 05:45:16 2005

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