Re: rdiff
"Paul Edwards" <[email protected]>
| Newsgroups | gmane.comp.version-control.cvs.bugs |
|---|---|
| Organization | BigPond Internet Services (http://www.bigpond.net.au) |
| Message-ID | <[email protected]> |
"Derek Robert Price" <[email protected]> wrote in message news:[email protected]... > >The other advantage rdiff has is that if two releases have > >different version numbers, but that is just a historical anomaly, > >there are no actual code changes, rdiff will not report any > >difference, while diff will show an "empty" change (which > >is usually of no interest to anyone). > > I've never verified the empty change behavior, but perhaps diff > shouldn't be displaying empty changes either. > > Regardless, I don't have time to do all this myself. :) > > Patches gratefully accepted! Test cases and new issues welcome as well. The following diff on cvs1-11-5 rectifies the problem for at least one variation of the diff command. If you go cvs diff -r xxx file.c then it will be quiet if there are no real changes. But still produce diffs if there are real changes. This doesn't fix the problem for cvs diff -r xxx -r yyy file.c though. And I didn't try it with plain "cvs diff file.c". Any ideas on where to fix it for the -r xxx -r yyy variation? Thanks. Paul. Index: diff.c =================================================================== RCS file: /cvs/ccvs/src/diff.c,v retrieving revision 1.93 diff -r1.93 diff.c 1006,1007c1006,1007 < else < return DIFF_DIFFERENT; --- > /*else > return DIFF_DIFFERENT;*/