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

Re: working copy storage for RA properties

From: Greg Stein <gstein_at_lyra.org>
Date: 2000-12-04 23:52:41 CET

On Mon, Dec 04, 2000 at 02:15:47PM -0600, Karl Fogel wrote:
> Branko =?ISO-8859-2?Q?=C8ibej?= <brane@xbc.nu> writes:
> > Greg Stein wrote:
> >
> > > 1) SVN/repository could be considered an RA property on the directory (not
> > > sure if we want to use a prop or keep the file, but it is possible)
> >
> > This may have to be per directory entry someday, if/when we decide to
> > add configurations. Not pushing for this right now, of course, I just
> > want to keep our options open.
> Hmmm. That's a good point.
> Perhaps it makes most sense to store the repository as an attribute on
> the entry (as in SVN/entries)? Files without a repository default to
> the dir's attribute, as usual...
> Again, Greg, assume there's a clean interface to getting/setting this
> information. Given that, what do you think of storing them on
> entries?

Seperate repositories at the file level seems over-the-top to me.
Per-directory is fine, but per-file? No way... that just feels like it will
get confusing as hell for the user.

Which file is from where? What happens when you add a file?

This just feels like a "we can build this, so let's do it" feature. I like
to take the pointer of view of "a feature exists because we *should*, not
because we *can*."

I'm -1 on per-file repositories.

(but yah: I presume there would be an API to get at that since non-WC code
cannot look into SVN/ ... and again: it would be libsvn_client that probably
needs it, rather than RA (since the URL determines the RA... chicken and egg
problem :-))


Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:16 2006

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