Noel L Yap writes:
>
> I think the stickiness issue is separate. If I "cvs up -r 1.1 -A file", I
> expect my current revision to be 1.1 and not be sticky. This is not what
> happens; although the working copy does become 1.1, it is still sticky.
I think your expectation is wrong. -A says to remove any sticky tag or
date that's currently on the file *before* doing the update, -r says
which version to update to. So, -A happens first and any existing
stickyness gets removed, then the update happens and you get a new
sticky.
> It seems you've been more thorough than I have. Looking at it another way, "cvs
> up -C file" should be equivalent to "cvs up -p -r <base-rev> file >file". If
> other flags (eg "-j") were specified, the command should be equivalent to "cvs
> up -p -r <base-rev> file >file; cvs up <other-flags> file".
That's the parallelism I was looking for. I agree completely.
-Larry Jones
Geez, I gotta have a REASON for everything? -- Calvin
