humpf.... I'll restate this since gmail was not nice with me this time :-(
Karl,
sure.
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...) used by the release. I
am able to know
exactly what code is impacted by the release (and it is a VERY small
subset of the trunk).
So I'd love to tag those files (and only those files) impacted by the
release. They won't be directories but files (which seems to be an
issue). This is doable (by scripting).
Then when an issue is detected on the release I want to be able to go
back in time to the release of those files (and only those), correct
them, and then switch back.
The easy way is to tag everything (trunk/mathos here) and then switch
back and forth from the release. One of the issue is that the trunk is
huge and the network not very fast...
Any ideas ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 6 22:58:44 2006