Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Module idea to help developers
- X-seq: zsh-workers 8238
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Module idea to help developers
- Date: Wed, 13 Oct 1999 16:20:14 +0000
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
I don't have time to do this myself right now, but:
It would be great if zsh could report something about what patches it has
applied to it. We could make a little module that implements a special
array parameter `patches', and stick a line in that module to identify each
patch, so that you could "print $patches" to see what was up.
We'd need a convention of some kind -- either it could be up to the patch-
applier to insert the article number by hand, or (better) the patch-maker
should supply a hunk for that module that adds a string he's made up. Such
a hunk would be likely to fail if some prerequisite patch was not present
(I suppose it would also be likely to fail in some cases of simultaneous
unrelated patching by two developers, but that would be easily resolved),
thus giving a clue about mistakes.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author