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

Re: cvs modules feature missing in subversion

From: Max Bowsher <maxb_at_ukf.net>
Date: 2004-12-30 20:20:49 CET

kfogel@collab.net wrote:
> Stephen Kennedy <stevek@gnome.org> writes:
>> There was some discussion on the subversion-users list about opening
>> an issue for the CVS modules feature and it was suggested that I post
>> to the devel list for more feedback.
>>
>> http://article.gmane.org/gmane.comp.version-control.subversion.user/22641
>>
>> There have been several posts to the list asking about this
>> functionality.
>> http://article.gmane.org/gmane.comp.version-control.subversion.user/22633
>>
>> I'm no svn hacker but it seems as though most of this issue revolves
>> around supporting directory hardlinks inside the svn filesystem.
>
> My feeling is that just because CVS happens to group a bunch of
> disparate functionality into one blurry thing called "modules",
> doesn't mean we have to see the world that way :-).
>
> It'll work better to consider each feature/enhancement individually
> (which seems to be what we're doing already, based on the issue
> numbers in the mails you refer to above). There's no overarching
> commonality to the CVS modules features, except the fact that they're
> all controlled from the CVSROOT/modules file.

... and that they are collectively a group of features we don't have much
support for.

I don't think there would be any point in having an issue saying "we need an
equivalent of CVS modules", but it would be wonderful if someone wanted to
analyse the uses to which CVS modules can be put, and generate a set of
case-studies of thinks which are difficult/impossible to do using
subversion.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 30 20:23:46 2004

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.