Mercurial > hg > xemacs-beta
comparison etc/BETA @ 136:b980b6286996 r20-2b2
Import from CVS: tag r20-2b2
author | cvs |
---|---|
date | Mon, 13 Aug 2007 09:31:12 +0200 |
parents | 34a5b81f86ba |
children | 9ad43877534d |
comparison
equal
deleted
inserted
replaced
135:4636a6841cd6 | 136:b980b6286996 |
---|---|
179 | 179 |
180 4. The configuration report illustrated above | 180 4. The configuration report illustrated above |
181 | 181 |
182 5. Any other unusual items you feel should be brought to the attention | 182 5. Any other unusual items you feel should be brought to the attention |
183 of the developers. | 183 of the developers. |
184 | |
185 ** Creating patches for submission | |
186 ================================== | |
187 | |
188 When making patches you should use the `-c', or preferably if your | |
189 diff supports it, `-u'. Using ordinary diffs like this are | |
190 notoriously prone to error (and this one won't in fact work, since | |
191 I've already applied a patch to this file so the line numbers probably | |
192 don't match up any more). | |
193 | |
194 $ diff -u old-file.c new-file.c | |
195 | |
196 -or- | |
197 | |
198 $ diff -c old-file.c new-file.c | |
199 | |
200 Also, it is helpful for me if you create the patch in the top level of | |
201 the XEmacs source directory: | |
202 | |
203 $ diff -u lwlib/xlwmenu.c~ lwlib/xlwmenu.c | |
204 | |
205 I prefer patches to be accompanied by an update (either a raw entry or | |
206 a patch) to the appropriate ChangeLog file, but it is not required. | |
207 | |
208 Also note that if you cut & paste from an xterm to an XEmacs mail buffer | |
209 you will probably lose due to tab expansion. The best thing to do is to | |
210 M-x cd to the appropriate directory, and issue the command `C-u M-!' from | |
211 within XEmacs. |