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

Re: svn commit: rev 1957 - trunk/subversion/include trunk/subversion/libsvn_wc

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-05-15 00:40:33 CEST

On Wed, May 15, 2002 at 12:23:35AM +0200, Branko Äibej wrote:
>...
> Just a minute. Are you doing all this work /instead/ of adding reference
> nodes to the filesystem? And this will all get ripped out once we have
> reference nodes? Sorry, but I don't like that at all.

The reference nodes are a different concept. While they might be able to do
inter-repository "modules", they won't be able to do intra-repos modules.
If/when those nodes arrive, the client-side modules would remain.

This approach is also a great way to handle modules. It is very user
approachable/editable (heck, even under revision control), and can easily be
handled entirely on the client side. No funky FS tricks.

Low dev bar. High functionality. Parity with CVS (maybe better).

> I also didn't find any design doc for this feature, discussing pros and
> cons and tradeoffs vs. reference nodes. I only remember one or two posts
> to the dev list, without any real conclusions.

All in the issue.

> (Can you point me to the relevant messages if I missed them? Thanks.)
>
> -1

Vetoes require a specific technical problem; preferably with solutions for
rectifying that problem. Is there something technically wrong with this
approach?

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 15 00:38:46 2002

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

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