So to tell you what I guess you need to know: we have one big project,
let's call it "mathos" for the example sake. So we have
http://...../trunk/mathos with a complex subdivision under this (a
large tree here). This is the main library that is shared by all
(developers, subjects,...). When a new project is started, it will
share some of the code from the main library (not all) plus some
specific code (usually in mathos/studies/project/...).
What I want to do is when I release a version of a project
(trunk/mathos/studies/project/...), I want to tag this PLUS the code
from the main (trunk/mathos/shared/whatever...). I am able to know
exactly what code is impacted by the release (
On 06 Feb 2006 11:01:36 -0600, firstname.lastname@example.org <email@example.com> wrote:
> Jérôme Besnard <firstname.lastname@example.org> writes:
> > First post to the list, so I apologize in advance :-)
> > My question is that I need to be able to tag a subset a my repository
> > as a release, and possibly switch back to this subset. This should be
> > quite easy, and the subversion book gives some hints, but I remain
> > quite not sure of the "subversion way" of doing this.
> > First let me describe the organisation of the code. We have one
> > repository, containing all our developments in the trunk. Then we
> > create, inside the trunk again, a "product" that only use a small
> > subset of the library. After compilation, we are of course able to
> > track the subset, and we know exactly what is used by the "binary"
> > product.
> > I'd like then to create a tag (let's say realase1.0 as usual) on this
> > subset, and come back to that subset for modifications or bug
> > issues...
> > The confusion is that it seems like I have to add the whole repository
> > as a tag (which is not such a big issue since it is cheap copies), but
> > then I am confused as how you get back to the subset.... The other way
> > around, selecting only the subset in the tag, seems to be better, but
> > when switching back, what will happen to the files not in the tag ?
> > I am setting up some tests here for this issue, but any insight from
> > the list would be invaluable :-)
> I think you'll need to diagram this out, with real path names, for us
> to understand what you're trying to do. What is "the library", for
> www.collab.net <> CollabNet | Distributed Development On Demand
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Feb 6 22:52:21 2006