-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
* On 11-01-02 at 14:34 * David T-G said.... > ...and then Nick Wilson said... > % > % Hi all, > % can anyone make sense of the output I'm getting when trying to use the > % %_patch? > > I get this all the time. Someone suggested a way to work around it, but > I've neither looked into it yet nor even retained the pointer :-( > > > Hmmm... You don't have a patchlist.c yet, so there's nothing yet to > patch. I don't usually get this... > > Oh, wait. You need Sec's patch-0.00.sec.patchlist.8.1.dtg (well, my > tweaked copy) to create patchlist.c so that later patches looking for it > will apply. I still use this and roll my own patchlist.c file because, > even if all patches used the PATCHES file that has returned to generate > patchlist.c itself, patches applied in order 1-2-3-4-5 end up being > listed in order 1-5-4-3-2 and I don't like that. > > Thanks I'll work on it! - -- Nick Wilson Tel: +45 3325 0688 Fax: +45 3325 0677 Web: www.explodingnet.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8PutnHpvrrTa6L5oRAgmOAKCHVx1F0bRmZP9lpvaz1lRasknc9wCgouji iI/U7wqxQ2gfiiPkrmsWw6k= =GbIv -----END PGP SIGNATURE-----
