[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: Ian Brockbank <Ian.Brockbank_at_wolfsonmicro.com>
Date: 2005-08-08 13:07:26 CEST

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
Received on Mon Aug 8 21:07:26 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.