Re: cvs update to branch with -f option

[Larry Jones]

address@hidden writes:
> 
> Each branch has a few developers working on a handful of files.  A
> developer working in a branch performs a checkout for the branch with the
> -f option, giving him an entire repository to work from consisting of the
> branched files, and the remainder of the repository from the main trunk.
> This developer then commits his changes to the branch for the other
> developers working in his branch.  The other developers working in that
> branch then perform an update to the branch with the -f option, again
> giving them the files committed by other developers in that branch and the
> remainder of the repository from the main trunk.
> 
> This method works well for us, except when the -f option is used, I would
> like to get the non-matching files from a tag, rather than from the main
> trunk (eg HEAD).

Branch the entire repository and stop using -f.  Branches are cheap,
particularly if you never commit anything on them.  And by branching
everything, you can branch wherever you want to get particular revisions
of certain files (e.g., at a particular tag).

-Larry Jones

I told her to expect you to deny everything. -- Calvin