[Top][All Lists]

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

[bug #17556] rev field in the CVSROOT/history file for "R" records is no

From: anonymous
Subject: [bug #17556] rev field in the CVSROOT/history file for "R" records is not meaningful (?)
Date: Mon, 28 Aug 2006 19:44:10 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20060212 Galeon/2.0.1


                 Summary: rev field in the CVSROOT/history file for "R"
records is not meaningful (?)
                 Project: Concurrent Versions System
            Submitted by: None
            Submitted on: Monday 08/28/2006 at 19:44 UTC
                Category: Bug Report
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
           Fixed Release: None
   Fixed Feature Release: None



Hi. I've been writing a tool that examines the history file, and I've
noticed notice that, for type "R" records (a file has been deleted),
the value in the revision field is not what I was expecting (and
wanting!): the number of the newly created "dead" revision.

Rather, it seems as if the revision number of the branch point is

For example, if I have a file on a branch with two revisions:

and I delete the file (thus creating the "dead" revision, the
history entry gives "1.2" as the revision in the "R" record written to
the history file. My expectation was for "".

Is this a bug? (If so, I already have a fix coded and tested :-).
See attached patchfile against 1.11.5)

I'm certainly HOPING that it's a bug, and that nothing anybody knows
of depends on the would-be buggy behavior...


  - Richard Geiger


File Attachments:

Date: Monday 08/28/2006 at 19:44 UTC  Name: patch  Size: 983B   By: None
patchfile (against 1.11.5 - not tested on more recent) with a proposed fix


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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