ndd@romeo.cs.duke.edu (Ned D. Danieley) (02/10/89)
Is there any way to tell what patches might have been applied to a given instance of the R3 sources? I've looked, and only kterm and patch seem to have a patchlevel.h. Shouldn't there be some indication in the top-level directory, or perhaps in lib? Ned Danieley (ndd@sunbar.mc.duke.edu) Basic Arrhythmia Laboratory Box 3140, Duke University Medical Center Durham, NC 27710 (919) 684-6807 or 684-6942
jim@EXPO.LCS.MIT.EDU (Jim Fulton) (02/20/89)
> Is there any way to tell what patches might have been applied > to a given instance of the R3 sources? Not beyond asking the person who maintains your sources. If you are comparing two versions of a particular file, you can look at the RCS keyword $XConsortium (we use it instead of $Header).
ndd@SUNBAR.MC.DUKE.EDU (Ned Danieley) (02/21/89)
> >> Is there any way to tell what patches might have been applied >> to a given instance of the R3 sources? > >Not beyond asking the person who maintains your sources. > >If you are comparing two versions of a particular file, you can look at the >RCS keyword $XConsortium (we use it instead of $Header). Unfortunately, I am the person who maintains my sources! What I was trying to do was decide which patches had been applied to the sources that I got from a local machine (unfortunately, their source person wasn't sure). I finally just looked at the id of a couple of files in the patches, and guessed that way. Shouldn't there be some overall version.h, or something, that could reflect version releases and the application of official patches? ned
jim@EXPO.LCS.MIT.EDU (Jim Fulton) (02/21/89)
> Shouldn't there be some overall version.h, or something, that could > reflect version releases and the application of official patches? Probably, but there have been so few patches.... I'd recommend either starting from scratch (take an R3 tape, fetch the patches, and apply the diffs) or going through the patches and looking at what has and hasn't been changed. Jim