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

[Tyler]

On Mon, Jun 14, 2004 at 11:43:45AM -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.

I'm not sure i understand the problem, but the stickiness of branch tags
may help you. If you set up your sandbox with all your files checked out
from the appropriate branches, commits will all go to the right places.
E.g.:

cvs up -rbranch1 file1
cvs up -rbranch2 file2
cvs up -A file_from_trunk

When you commit, file1's change will be committed to branch1, file2's to
branch2 and file_from_trunks to the trunk. Is this what you're looking
for?

If you need to reproduce it, you could write a script to do the initial
checkout.

Note that this approach is awfully fragile, perhaps even dangerously so,
especially if you expect a whole room full of developers to do it
without errant commits.

tyler