Yeah, this is what made me choose to keep them all in one repository in
the first place...
I'm thinking that I'll end up splitting off my self-contained projects
into their own repositories and keeping the rest as-is.
On Jun 28, 2005, at 9:41 AM, Scott Lawrence wrote:
> On Tue, 2005-06-28 at 09:27 -0300, Ben Jackson wrote:
>> Currently I have all of my projects in one SVN repository. This seemed
>> like a good idea at first as there were some shared code libraries
>> that
>> were used across multiple projects, but the log is getting cluttered,
>> and I'm thinking it might be a good idea to split the repository by
>> project. Is this a good idea? Thanks,
>
> We made the opposite choice initially - we made each of several
> libraries its own repository. We're now going through the work to
> merge
> them again (which svn supports remarkably well, actually).
>
> The problem we found is that it's a pain to track what rev of each
> library is needed for each dependent component.
>
> --
> Scott Lawrence, Consulting Engineer
> Pingtel Corp. http://www.pingtel.com/
> +1.781.938.5306 x162 or sip:slawrence@pingtel.com
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 28 15:11:36 2005