Re: Updating file versions from 1.x to 2.x

[Laird Nelson]

Michael Bailey wrote:
> I've been asked to update file versions for all files on a branch to 2.0
> Although I realise this is not the cvs way, would it be A Bad Thing?

{sigh} It's a shame you're dealing with a boss who most likely has only
ever used or heard of SCCS, which doesn't have labeling/tagging
facilities, and is hence usually the culprit for people's wanting to
change opaque revision numbers to 2.0.  Oh well.

It shouldn't be a bad thing.  The command we had to use around here
(when we were working with just such a boss) was something involving cvs
commit -r2.0 -f *.yourfileshere in each directory.  This is always a
sign that someone is ordering you to do something that they don't
understand, but it works.

(Far saner, just so I say it and get it out of my system, would be to do
this:

  cd /your/sandbox
  cvs update -d -P -A
  cvs tag A_LABEL_THAT_MAKES_SENSE

...and then if you ever need to get a file corresponding to that label,
you'd do this:

  cd /your/sandbox
  cvs update -r A_LABEL_THAT_MAKES_SENSE theFile.txt

This is usually the only use case that your modern version control
system ignorant manager is trying to accomplish, and so upping
everything to revision 2.0 is the wrong way to go, as you indicated you
know.)

Cheers,
Laird

--
W: address@hidden / P: address@hidden
http://www.amherst.edu/~ljnelson/
Good, cheap, fast: pick two.