Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 16669

Summary: gendiff man page example
Product: [Retired] Red Hat Linux Reporter: giulioo
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 7.1Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-08-21 09:32:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description giulioo 2000-08-21 09:31:17 UTC
The man page of gendiff explains very well how gendiff works, but then it 
makes an example that is not a perfect choice for the place where it's 
being done (a man page):

===
 I.e. if you were
       going to edit somefile.cpp, copy it  to  somefile.cpp.save
       before  editing  it.   Then  edit  the  first  copy (some-
       file.cpp).
 
       After editing all the files you need to edit in this fash-
       ion, enter the directory one level above where your source
       code resides, and then type
           $ gendiff somedirectory .orig > mydiff-orig.patch
===

if you backup your files with .save then gendiff wants .save as extension, 
not .orig.
Since this is a manpage, where new users will look at, it would be better 
to use the backup extension consistently.

Comment 1 Jeff Johnson 2000-08-24 15:57:18 UTC
FIxed in rpm CVS. Thanks for noticing and reporting.