From: Clint Adams <schizo@debian.org>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: Module idea to help developers
Date: Wed, 13 Oct 1999 14:42:33 -0400 [thread overview]
Message-ID: <19991013144233.A23715@dman.com> (raw)
In-Reply-To: <991013162014.ZM14485@candle.brasslantern.com>
> 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.
next prev parent reply other threads:[~1999-10-13 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-13 16:20 Bart Schaefer
1999-10-13 18:42 ` Clint Adams [this message]
1999-10-14 3:48 ` Bart Schaefer
1999-10-14 10:52 ` Oliver Kiddle
1999-10-14 12:27 ` CVS again (Re: Module idea to help developers) Adam Spiers
1999-10-15 13:57 ` Clint Adams
1999-10-15 14:08 ` Andrej Borsenkow
1999-10-15 14:19 ` Clint Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19991013144233.A23715@dman.com \
--to=schizo@debian.org \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).