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

Re: Archiving Projects (End-Of-Life)

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Tue, 14 Dec 2010 12:00:39 +0100

On Tue, Dec 14, 2010 at 11:58 AM, Cooke, Mark <mark.cooke_at_siemens.com> wrote:
>> On Tuesday 14 December 2010, Cooke, Mark wrote:
>> > I'd be interested in any strong arguments for using one
>> > repo over many!
>> -----Original Message-----
>> From: Ulrich Eckhardt [mailto:ulrich.eckhardt_at_dominolaser.com]
>> Sent: 14 December 2010 10:53
>> To: users_at_subversion.apache.org
>> Subject: Re: Archiving Projects (End-Of-Life)
>> You don't need svnadmin to create a new project.
>> That was simple! :'D
>> Uli
> ...but I don't see that as a problem for us, it's just a little pain
> occasionally for a big gain in the end.
> Plus, for us, we usually have linked Trac environments, so that needs to
> be created as well.  In fact, having linked trac projects is another
> reason why I like the lack of revision number churn caused by unrelated
> projects.
> ~ mark c

In our case, code sometimes migrates from one project to another (the
projects are closely related, or put another way: there are a lot of
dependencies among them).

For instance: we have a "common" project, with the common utilities
used by other projects. Sometimes, some new utility code is written in
one of the projects (starts out as being useful for that single
project), and after a while, they see that it could be useful for
other projects as well. So the stuff is moved to the common project,
without losing history etc.

We don't care about revision number churn ...

Received on 2010-12-14 12:01:35 CET

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.