Re: how to update tagged files?

[Eric Siegerman]

Short answer: No, there isn't a way to do "cvs update -r<tag>"
without deleting the files that don't have the tag.

On Tue, Aug 28, 2001 at 01:26:05PM +0100, JM Murillo wrote:
> [He wants to tag only the files he's changed, and use the tag
> to propagate his changes into a second sandbox.  It doesn't
> work because "cvs update -r<TAG>" removes files that don't have
> TAG.]
>
> Is
> there any way to do it without removing the other files and without tagging
> the other files? I know that is posible do it individually for each file,
> but i want to do it for a entire directory in the working copy.

To do specifically that?  No.  And you'll run into more problems
when you try to commit from the second sandbox -- it won't let
you because of the sticky release (aka non-branch) tag.

If you describe the goals you're trying to accomplish, I'm sure
we can find a way.  Offhand, I'd guess that the answer will be
one of:
  - ignore the problem because it isn't really a problem, or
  - use a branch
But of course, at this point I don't know which of those is
appropriate, if in fact either one is :-)

> There is a option
> at update command that do something like this, but when i do the update with
> this option, the other files in the second working copy are tagged with the
> same tag automatically.

There is?!?  Which one?

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea.
        - RFC 1925 (quoting an unnamed source)