Jim Doyle writes: > > Is there a chance the cvs log features recently added can be further > extended to work across branches? To a user, I think 1.3, 1.3.2.1, > 1.3.2.2, ... looks like a legal sequence that cvs log should be able to > follow. Would it make sense to allow ranges A::B, where A precedes B on > the same branch, *or* A::B' is itself a legal range, where B' is the > origin of the branch B is on? Then the code could walk backwards from > B, jumping to the branch origin of B while A has fewer "numdots" than > B. Does this make sense when coming at it from the point of view of > implementing CVS?
Yes, I noticed that as a potential problem when I was adding the :: support, but I didn't worry about it too much since I don't recall anyone ever reporting it. Unfortunately, the code is full of assumptions that the starting and ending revision numbers have the same number of dots, so there's a lot of rewriting to do. It's also not quite as simple as it might seem, since I believe that 1.2:4.5.6.7.8.9 should also be a valid range, no? (All revisions with a single dot are on the trunk, reguardless of the major revision number; on other branches, the major componenents of the revision number must be exactly equal.) -Larry Jones I wonder what's on TV now. -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
