[Top][All Lists]

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

update command change behavior

From: jbreed
Subject: update command change behavior
Date: Wed, 28 May 2008 10:49:19 -0500 (CDT)

>Submitter-Id:   net
>Originator:     Jeff Reed
>Confidential:  no
>Synopsis:      update performs updates that are not required
>Severity:      serious
>Priority:      high
>Category:      cvs
>Class:         sw-bug
>Release:       1.11.23
System: Linux cvs2.acme.intrinsity.com 2.6.9-42.ELsmp #1 SMP Sat Aug 12 
09:39:11 CDT 2006 i686 i686 i386 GNU/Linux
Architecture: i686

We use cvs update in the following manner:
% cvs -n -q update -r release-tag
To determine if things have changed on the branch since the last installation. 
We work exclusively on branches.  In this particular scenerio there were no
changes since the last time the module was taged with release-tag.  version
1.11.23 shows that there are updates required.  1.11.22 shows that no updates
are required.
Using a test repository:
% cvs co test
% cd test
% cvs tag -b branch
% cvs update -r branch
% mkdir update-bug
% cvs add update-bug
% cd update-bug
% for i in this that and the other
        echo $i > $i
% cvs add *
% cvs ci -m "initial check in"
% cvs tag -F release-tag
% cvs -n -q update -r release-tag
U and
U other
U that
U the
U this
Since revision tag release-tag and branch at this point should be identical
the above behavior is broken.  Previously, released versions of cvs do not 
have this problem.

reply via email to

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