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

RE: One repository per project or one to rule them all?

From: Dale Worley <dworley_at_pingtel.com>
Date: 2005-06-28 15:30:27 CEST

> 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.


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:35:54 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.