FREEBSD-upgrade (18102) | FREEBSD-upgrade (18815) |
---|---|
1This directory contains virgin copies of the original distribution files 2on a "vendor" branch. Do not, under any circumstances, attempt to upgrade 3the files in this directory via patches and a cvs commit. 4 5To upgrade to a newer version of groff, when it is available: 6 1. Unpack the new version into an empty directory. 7 [Do not make ANY changes to the files.] 8 --- 5 unchanged lines hidden (view full) --- 14 cvs import -m 'Virgin import of FSF groff v1.10' \ 15 src/contrib/groff FSF v1_10 16 17 3. Follow the instructions printed out in step 2 to resolve any 18 conflicts between local FreeBSD changes and the newer version. 19 20Do not, under any circumstances, deviate from this procedure. 21 | 1This directory contains virgin copies of the original distribution files 2on a "vendor" branch. Do not, under any circumstances, attempt to upgrade 3the files in this directory via patches and a cvs commit. 4 5To upgrade to a newer version of groff, when it is available: 6 1. Unpack the new version into an empty directory. 7 [Do not make ANY changes to the files.] 8 --- 5 unchanged lines hidden (view full) --- 14 cvs import -m 'Virgin import of FSF groff v1.10' \ 15 src/contrib/groff FSF v1_10 16 17 3. Follow the instructions printed out in step 2 to resolve any 18 conflicts between local FreeBSD changes and the newer version. 19 20Do not, under any circumstances, deviate from this procedure. 21 |
22To make local changes to tcpdump, simply patch and commit to the main | 22To make local changes to groff, simply patch and commit to the main |
23branch (aka HEAD). Never make local changes on the FSF branch. 24 25All local changes should be submitted to "jjc@jclark.com" for 26inclusion in the next vendor release. 27 28pst@freebsd.org - 7 Sep 1996 | 23branch (aka HEAD). Never make local changes on the FSF branch. 24 25All local changes should be submitted to "jjc@jclark.com" for 26inclusion in the next vendor release. 27 28pst@freebsd.org - 7 Sep 1996 |