Tickets :: Comment on [#5284] Move to subversion for Horde code repository

* Your Email Address
* Spam protection	Enter the letters below: .__..__..___. __. __. \| \|\| \| \| (__ (__ \|__\|\|__\ \| .__).__)
Comment	>>> After taking a look at the current SVN repository, I changed my mind > >>> and think we should setup separate modules for each Horde app. Having > >>> all tags and branches for all horde modules ever in branches/ and > >>> tags/ looks really cluttered. I think it's worth not being able to > >>> svn mv between horde modules for the benefit of a cleaner layout. > >> > >> We could still svn mv/copy between them, unless we really made them > >> completely separate repositories. There is nothing hardcoded in > >> subversion about trunk/tags/etc - it's just a convention. We could to > >> a top-level list of modules with their own trunk, tags, branches > >> dirs, or we could do subdirs inside the /tags and /branches dirs just > >> like we have inside /trunk. > > > > I would prefer top-level modules, then trunk/tags/branches. But we > should make sure first that Chora works fine with that. :)
Attachment
Watch this ticket