I have three pretty large projects that do occassionally have some very
large commits. When I first setup I had all in one repository, and the
log viewing took a long time. It was almost painful. So I broke them
out into separate repositories. The very few files that do get shared
can be hand modified on the individual developer workstation and
committed into each repository (yes, two commits instead of one). But I
have less than 10 shared files out of repositories containing at least
2500 files. So it works for me.
Now, log viewing works great, backup jobs are easy to monitor, managing
of the projects is easier, and we are all happy as clams at high tide.
Granted - some of these benefits are my perceptions, but we use it
because it allowed us to be flexible. And THAT, my friends, is why I
like Subversion.
$.02.
Regards,
Frank
Dale Worley wrote:
>>From: Ben Jackson [mailto:ben@incomumdesign.com]
>>
>>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,
>>
>>
>
>Unless you absolutely never move code between the projects, use one
>repository, because moving code between repositories is a nuisance.
>
>But why is the log a problem? If you do "svn log" on a directory that is
>the root of a project, you should only see the changes in the project.
>
>Dale
>
>
>---------------------------------------------------------------------
>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:53:01 2005