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

Re: early reflections on subversion methodology

From: Robert P. J. Day <rpjday_at_mindspring.com>
Date: 2005-07-30 14:49:01 CEST

On Sat, 30 Jul 2005, Thomas Beale wrote:

> Frank Gruman wrote:

> > All in all, I think the subversion developers are approaching it
> > properly in allowing freedom of repository layout. If you do want
> > something more 'standardized', I think I saw another post
> > referring to building a __client__ that enforced whatever
> > structure you want. That's the beauty - you can take the server
> > and data inside of it and put whatever top end on it you want.
> > But not at the server level.
>
> I think that one obvious way to implement what I am suggesting is
> indeed in client tools.

i might be missing your point but i see one possible issue with your
moving the support for branching/tagging/whatever into the client
tools, rather than just leaving it where it is as part of the regular
directory structure.

as more than one person has pointed out, there's nothing magical about
directories named "Branches" or "Tags" or "Releases" -- it's all in
the way you treat them, that's all.

and while any client tool would most likely want to have some
pre-defined set of perspectives like main, branches, tags and so on,
the directory structure effortlessly let's you define certain views of
the repository as, say, "Rob's Wild and Crazy Ideas" and stuff like
that.

will your hypothetical client tool be able to handle that kind of
flexibility?

rday

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 30 14:50:56 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.