[EMAIL PROTECTED] (Larry Jones) wrote in message news:<[EMAIL PROTECTED]>... > David Carson writes: > > > > I'm sure there is some complication involved, but it is apparently > > possible. The "cvs rdiff -r<revA> -r<revB>" syntax handles this > > problem correctly, going from <revA> to <revB> even if from trunk to > > branch. As long as point A is an ancestor of point B, then there is > > only one way to get to B from A. > > But rdiff doesn't care whether A is an ancestor of B or not, it compares > *any* two revisions. The complication is determining whether A is an > ancestor of B, B is an ancestor of A, or neither is an ancestor of the > other.
Granted. I agree that the problem is not trivial. But, are you saying that it is not possible with CVS? I would reiterate my earlier assertion that a version control system must be able to perform this function to call itself fully functional. David _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
