Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Module idea to help developers

X-seq: zsh-workers 8240
From: Clint Adams <schizo@xxxxxxxxxx>
To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Module idea to help developers
Date: Wed, 13 Oct 1999 14:42:33 -0400
Cc: zsh-workers@xxxxxxxxxxxxxx
In-reply-to: <991013162014.ZM14485@xxxxxxxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
References: <991013162014.ZM14485@xxxxxxxxxxxxxxxxxxxxxxx>

> 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.

Assuming all these packages will end up in the source, increasing
release frequency or providing CVS snapshots (with the date
automatically appended to the version number) would help a bit.

What you're proposing seems more suited for patches that won't be
incorporated.

Follow-Ups:
- Re: Module idea to help developers
  - From: Bart Schaefer

References:
- Module idea to help developers
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author