[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: ci/co on HEAD for specific files in a branch?

From: Jim.Hyslop
Subject: RE: ci/co on HEAD for specific files in a branch?
Date: Mon, 14 Jun 2004 13:58:52 -0400

Doug Lee wrote:
> Is there a way for me to specify that certain files should 
> checkout when I checkout a branch but should commit to the 
> trunk when committed?  In other words, I have one or more 
> branches that contain a few files that should have only one 
> development path.  Specifically, the HTML document describing 
> the project should not branch but should be a part of all 
> branches along with the code.
In other words, you want it to remain on the trunk.

One possibility would be to hook into the 'taginof' script, and have it fail
if anyone tries to apply a branch tag to the file. It will make tagging
branches rather cumbersome, as the developers will have to tag everything
*except* the document.

I've run into the same problem. In my case, we use a file called 'tags.txt'
in which we record some information about when and why a tag was applied.
Currently, we just rely on developers remembering to 'update -A tags.txt'
before updating the tag information. As has been pointed out, though, it is
quite fragile.

I've occasionally toyed with the idea of somehow flagging a file as
"non-branchable". I'm not sure how that would be implemented, though;
perhaps a new RCS keyword in the file? For these files, CVS would consider
any branch tag to refer to the trunk. So, you'd still update to the branch,
but the file itself always effectively stays on the trunk.

Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. (
Columnist, C/C++ Users Journal (

reply via email to

[Prev in Thread] Current Thread [Next in Thread]