[Lxr-dev] [ lxr-Bugs-3434724 ] CVS.pm does not work with branching tags
Brought to you by:
ajlittoz
From: SourceForge.net <no...@so...> - 2011-11-08 01:38:55
|
Bugs item #3434724, was opened at 2011-11-07 17:38 Message generated for change (Tracker Item Submitted) made by bladedoyle You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3434724&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Blade Doyle (bladedoyle) Assigned to: Nobody/Anonymous (nobody) Summary: CVS.pm does not work with branching tags Initial Comment: LXR version: 0.9.10 No indexes are created for branched tags Using CVS.pm ---------------------- The "CVS.pm" code for "sub parsecvs" does not work with branching tags. No indexes are created for them. For branches RCS version numbers contain a "0" to indicate they are a branch. When mapping 'symbols' to a real revision number the code needs to find what actual revision number for a branching tag is. Currently for a branched tag the parsecvs function looks through the rcs file and finds that a branching tag (ex: FOO) is associated with revision (ex: 1.2.0.3). But that isn't an actual revision number 1.2.0.3. So we need some additional code in the parsecvs function to find the actual revision number for branched tags. I am attaching an example of some code that appears to solve the problem. (I don't claim to be an expert on the RCS file format but I looked at a few rcs files and found a pattern that seems to hold up) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3434724&group_id=27350 |