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

Re: Storing Subversion repositories within another Subversion repository.

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 24 Jul 2009 12:29:45 -0400

On Fri, Jul 24, 2009 at 12:15, Phillip
Dann.Ward<Phillip.Dann.Ward_at_silver-atena.com> wrote:
> It is an empty repository (i.e. empty branches/tags/trunk folders, etc)
> created using "svnadmin create".
>
> I intend to do absolutely nothing with this empty repository once it is in
> my development repository.
>
> I was just wondering if there might be any side effects of doing this such
> as the development repository getting 'corrupted' if Subversion gets
> confused by seeing the empty repository inside it or perhaps the empty
> repository not being exported properly because Subversion thinks that it is
> part of (rather than just simply stored in) the development repository.

I don't see the point. svnadmin create only takes a few seconds to
run, probably less time than it would take to check out or export the
contents from the repository you put it into.

>>>> On 24/07/2009 at 17:06, in message <20090724160614.GA6301_at_cryptio.net>,
>>>> Tyler Roscoe <tyler_at_cryptio.net> wrote:
> On Fri, Jul 24, 2009 at 09:18:42PM +0530, Phillip Dann.Ward wrote:
>> Would there be any side-effects of storing an empty, static subversion
>> repository within another subversion repository?
>
> What exactly would you be storing? Empty branches/tags/trunk folders?
> conf/db/hooks/locks folders created by svnadmin create?
>
> What do you intend to do with these files after they're in your repo?
>
> tyler
>
>
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2375279

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-24 18:30:55 CEST

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.