[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: update -j -j gets unwanted files

From: Jacob Weber
Subject: RE: update -j -j gets unwanted files
Date: Tue, 25 Oct 2005 15:40:43 -0400

Forgot to mention: this only happens when the directory does not yet exist
on the branch. So the first command:
        cvs checkout -r branchName project/dir
doesn't get anything; it leaves an empty directory.

So I actually have to do:
        cvs checkout -j branchName -j tagName project/dir
(instead of update) in order to revert this directory to the tagged version.
Since the directory doesn't exist, could this be causing the checkout to
grab unwanted files? Is there a way to avoid this?


-----Original Message-----
From: address@hidden
[mailto:address@hidden Behalf Of
Jacob Weber
Sent: Tuesday, October 25, 2005 3:27 PM
To: info-cvs
Subject: update -j -j gets unwanted files

I have a directory on the main trunk, whose files were tagged at one point
in the past. Now I am working in a branch, and I would like to revert that
directory to the tagged version. I want to be able to commit this change to
the branch, so I don't want sticky tags.

This is what I tried:
cvs checkout -r branchName project/dir
  (to get the latest version of the directory on the branch)
cvs update -j branchName -j tagName
  (to revert the changes)

For the tagged files, this gets the right versions. The problem is, this
also pulls down files that were added to the trunk after the tagging. These
files have no tags, but they were still retrieved in the update. I would
expect this behavior if I passed -f to cvs update ("Force a head revision
match if tag/date not found"), but I didn't (and it's not in my .cvsrc

Any idea why? Thanks,

Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]