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

* Your Email Address
* Spam protection	Enter the letters below: .__..__..__ . ,.__ \| \|[__][ __ \./ [__) \|__\|\| \|[_./ \| \|
Comment	>> we could move all FW_3 apps under the FW_3 horde in the repository, > >> so that they are useable as-is. Then we could re-engineer HEAD to > >> simply work while expecting things to be side-by-side. That way we > >> get reasonable behavior for the (not so huge) set of FW_3 apps, and > >> can break BC for HEAD and have a nicer structure overall, period. > > > > But that would meen that anybody checking out the horde module from > FW_3 would get all apps checked out too, correct? > > > > 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.
Attachment
Watch this ticket