Annotated edit history of
gendiff(1) version 1 showing authors affecting page license.
View with all changes included.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
GENDIFF |
|
|
2 |
!!!GENDIFF |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
SEE ALSO |
|
|
7 |
AUTHOR |
|
|
8 |
---- |
|
|
9 |
!!NAME |
|
|
10 |
|
|
|
11 |
|
|
|
12 |
gendiff - utility to aid in error-free diff file generation |
|
|
13 |
!!SYNOPSIS |
|
|
14 |
|
|
|
15 |
|
|
|
16 |
__gendiff__ |
|
|
17 |
__ |
|
|
18 |
!!DESCRIPTION |
|
|
19 |
|
|
|
20 |
|
|
|
21 |
__gendiff__ is a rather simple script which aids in |
|
|
22 |
generating a diff file from a single directory. It takes a |
|
|
23 |
directory name and a |
|
|
24 |
__patch__ program to recreate the |
|
|
25 |
changes. |
|
|
26 |
|
|
|
27 |
|
|
|
28 |
The usual sequence of events for creating a diff is to |
|
|
29 |
create two identical directories, make changes in one |
|
|
30 |
directory, and then use the __diff__ utility to create a |
|
|
31 |
list of differences between the two. Using gendiff |
|
|
32 |
eliminates the need for the extra, original and unmodified |
|
|
33 |
directory copy. Instead, only the individual files that are |
|
|
34 |
modified need to be saved. |
|
|
35 |
|
|
|
36 |
|
|
|
37 |
Before editing a file, copy the file, appending the |
|
|
38 |
extension you have chosen to the filename. I.e. if you were |
|
|
39 |
going to edit somefile.cpp and have chosen the extension |
|
|
40 |
|
|
|
41 |
|
|
|
42 |
After editing all the files you need to edit in this |
|
|
43 |
fashion, enter the directory one level above where your |
|
|
44 |
source code resides, and then type $ gendiff somedirectory |
|
|
45 |
.fix |
|
|
46 |
|
|
|
47 |
|
|
|
48 |
You should redirect the output to a file (as illustrated) |
|
|
49 |
unless you want to see the results on stdout. |
|
|
50 |
!!SEE ALSO |
|
|
51 |
|
|
|
52 |
|
|
|
53 |
diff(1), patch(1) |
|
|
54 |
!!AUTHOR |
|
|
55 |
|
|
|
56 |
|
|
|
57 |
Marc Ewing |
|
|
58 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.