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

Re: Re: Problem importing a project

From: Jeffrey Kesselman <jeffpk_at_gmail.com>
Date: 2005-08-08 22:18:15 CEST

Interesting and a good point, thanks!

Maybe I just need to reorganize my repository.

Im somewhatnew to SVN, are there admi ncommands that would let me fo
the equivalent of unix mkdir and move to move the whole tree down a
coupel of directories?


On 8/8/05, Ian Brockbank <Ian.Brockbank@wolfsonmicro.com> wrote:
> Hi Jeffrey,
> > Id be interested to know what "best practoice" is violated by giving
> > each projectits own repository. In our case, where each project is
> > unique and has a unique list of qualified users, it seemd not only the
> > simpelst but also the most obvious way to organize our SVN server.
> The "best practice" that's violated by having the project at the root of
> the repository is having areas for trunk (mainline development),
> branches
> (side developments which may or may not get merged in to mainline at a
> later
> date) and tags (remembered versions, e.g. releases). In Subversion,
> these
> are just directory locations. Following this model you would have your
> project at http://server/repos/trunk instead of http://server/repos
> HTH,
> Ian Brockbank
> Applications Software Team Leader
> e: ian.brockbank@wolfsonmicro.com / apps@wolfsonmicro.com
> scd: ian@scottishdance.net
> t: +44 131 272 7145
> f: +44 131 272 7001
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Aug 9 06:18:15 2005

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

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