jcs.org
mutt stable branch with some hacks
1From roessler@does-not-exist.org Wed Nov 7 11:49:56 2001
2Date: Wed, 7 Nov 2001 11:49:56 +0100
3From: Thomas Roessler <roessler@does-not-exist.org>
4To: mutt-dev@mutt.org
5Subject: To those shipping patches (v2)
6MIME-Version: 1.0
7Content-Type: text/plain; format=flowed
8Status: RO
9Content-Length: 1273
10Lines: 34
11
12You folks have convinced me that the old patchlist was almost the
13right way to go for mutt identifying what patches have been applied.
14
15Thus, I've implemented this scheme (and will commit it to the CVS
16in a moment): There's a new file called PATCHES in the source tree,
17which will be empty in the official distribution.
18
19This file's format is one patch ID per line. Patch IDs should be
20the same as the file names used for distributing patches. The
21format for these file names should be this:
22
23 patch-<version>.<initials>.<patch-description>.<patchlevel>
24
25That is, Vsevolod's NNTP patch for mutt-1.3.42 could be named like
26this:
27
28 patch-1.3.42.vvv.nntp.1
29
30 From PATCHES, patchlist.c will be automatically generated. In
31order to properly construct PATCHES, please include the following
32chunk with your patch, replacing <your-id-here> by your patch ID.
33
34------------------------------snip------------------------------
35--- PATCHES~ Tue Nov 6 19:59:33 2001
36+++ PATCHES Tue Nov 6 19:59:42 2001
37@@ -1,0 +1 @@
38+<your-id-here>
39------------------------------snip------------------------------
40
41The patch IDs will be displayed when mutt is run with the 'v'
42command line switch.
43
44--
45Thomas Roessler http://log.does-not-exist.org/
46