[cvsnt] Re: What is required for server to pickup updated CVSROOTinformatiion.

Bo Berglund Bo.Berglund at system3r.se
Fri Oct 28 13:13:35 BST 2005

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

I think you misunderstood my question.
I use modules definitions fro virtual modules that *include* common files
below the top module folder (using ampersand modules). Thus I have many
instances of the same common files in different modules. A module might
check out only 2-3 files from a common folder and another 3-4 overrlapping
or separate files as needed by that module.

When we tag the project we do it from the top level of the virtual module
sandbox and it will tag all the files including the ones sitting in the
common folders. But we only tag the files in common that are actually used
by the module and thus checked out for this module.
This works well.

If a modification is done to a specific file in one project then a simple
update in the other project will retrieve the new revision. But this is
controlled by the developer. He might not want to include these changes
just yet so he puts off the update.
When he tags the module then he will tag exactly what he used for his own
state and he is not affected by changes in another project until he updates.

Also we make sure not to pollute a lot of files not part of a specific
project with project related tags.

So what I asked about is why you state that a virtual module cannot be tagged
using a regular tag command from teh sandbox?


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Oliver Giesen
Sent: den 28 oktober 2005 09:30
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] Re: What is required for server to pickup updated CVSROOTinformatiion.

Bo Berglund wrote:

> Why can't you use tag on a virtual module?

Because Tag would not accept a target argument that does not physically
exist in my sandbox. That's the whole point of having the two commands,
isn't it?

> I do this without problems a lot...


I'm not talking about checking out the module and then tagging all the
files in your sandbox. I often have module definitions that overlap a
lot (without actually conflicting) and I have them checked out
simultaneously, e.g. for each project I have a module definition that
includes all of the dependent library modules. All projects are checked
out to the same root folder and thus I typically only ever have one
instance of every shared module checked out at a time even though I
might be working on multiple projects that depend on it. When I want to
tag a project and all dependencies I cannot use Tag from the sandbox
root as that would tag all of my other projects and their individual
dependencies, too. Only RTag on the virtual module would be able to tag
only what I want but that is often not feasible due to the already
discussed HEAD-affinity issues of RTag...


----  ------------------
JID:  ogiesen at jabber.org
ICQ:  18777742	(http://wwp.icq.com/18777742)
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook