gnustep/libs-base
0
0
Fork 0
mirror of https://github.com/gnustep/libs-base.git synced 2025-04-23 00:41:02 +00:00
Code Issues Projects Releases Packages Wiki Activity

Update from libobjects terminology to gstep-base.

Browse source 
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk@1823 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
mccallum 1996-09-24 16:06:49 +00:00
parent 08a7dc30ce
commit e65606381a
1 changed files with 12 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
Admin/HOWTO-patches
View file

@ -1,21 +1,23 @@
Directions for creating a libobjects patch
Directions for creating a GNUstep Base Library patch
---------------------------------------------------------------
0. Have somewhere an old, pristine version of the libobjects
directory. We'll assume this directory is called "libobjects-old".
0. Have somewhere an old, pristine version of the gstep-base
directory. We'll assume this directory is called "gstep-base-old".
1. Have somewhere a new, changed version of the libobjects directory.
We'll assume this directory is called "libobjects", and that it has
the same parent directory as "libobjects-old"
1. Have somewhere a new, changed version of the gnustep-base directory.
We'll assume this directory is called "gstep-base", and that it has
the same parent directory as "gstep-base-old"
2. cd to the common parent directory of your two libobjects directories.
2. cd to the common parent directory of your two gstep-base directories.
3. Create the patch with
diff -r -c2 libobjects-old libobjects >my.patch"
diff -r -N -u gstep-base-old gstep-base >my.patch"
The `-u' requests a `unified-diff' style patch. If your version of
diff doesn't support this, pass `-c2' instead of `-u'.
4. Add a GNU-style ChangeLog entry to the top of the patch. You can
do this from within emacs using M-x add-change-log-entry.
do this from within emacs using M-x add-change-log-entry.
5. If you want to include a short note of explanation to me
personally, put it at the top, above the ChangeLog entry.
@ -27,7 +29,7 @@ personally, put it at the top, above the ChangeLog entry.
For a beautiful example from Adam Fedor, see the file example.patch.
If you send me multiple patches to the same file between releases of
libobjects, please diff against a version that has your previous patches.
gstep-base, please diff against a version that has your previous patches.
[I just threw these directions together. If you have constructive
suggestions for improving these directions, please send them to me.