Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!darwin.sura.net!haven.umd.edu!uunet!gatech!howland.reston.ans.net!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!nate From: nate@cs.montana.edu (Nate Williams) Subject: Re: Patchkit info needed Message-ID: <1993Mar23.214931.10811@coe.montana.edu> Sender: usenet@coe.montana.edu (USENET News System) Organization: CS References: <1993Mar23.201526.20984@news.eng.convex.com> Date: Tue, 23 Mar 1993 21:49:31 GMT Lines: 26 In article <1993Mar23.201526.20984@news.eng.convex.com> mccrorey@convex.com (Martin McCrorey) writes: > >I would like to know how to determine what is changed by each patch. >A list of files changed by a particular patch would be sufficient. >If I am supposed to be able to get this from the FILESwhatever file >included with the patchkit, then I need to know how to interpret >this file, because it isn't obvious to me. I thought it was pretty obvious, but DIR means a new directory was created by the patchkit NEW mean a new file was created by the patchkit PATCH # means that the patchkit has modified the file, and the # means how many times it's been modified. > If you want to know what EACH patch modifies, then look at the PATCH file in each seperate patch directory. Nate -- osynw@terra.oscs.montana.edu | Still trying to find a good reason for nate@cs.montana.edu | these 'computer' things. Personally, work #: (406) 994-4836 | I don't think they'll catch on - home #: (406) 586-0579 | Don Hammerstrom