From: Zack Brown <zbrown@tumblerings.org>
To: linux-kernel@vger.kernel.org
Cc: Matthias Andree <matthias.andree@gmx.de>
Subject: Re: lk-changelog.pl 0.96
Date: Mon, 14 Apr 2003 09:29:19 -0700 [thread overview]
Message-ID: <20030414162919.GQ2091@renegade> (raw)
In-Reply-To: <20030414154901.GC8125@merlin.emma.line.org>
On Mon, Apr 14, 2003 at 05:49:01PM +0200, Matthias Andree wrote:
> On Sun, 13 Apr 2003, Zack Brown wrote:
>
> > Too bad for me, I was hoping to use that data structure as a complete list
> > of email -> name translations for changelog entries. Maybe you could
> > include them anyway as commented out entries in the data structure? That
> > would give your script the added benefit of being harvestable for other
> > purposes, but wouldn't sacrifice the regex speed enhancements.
>
> How about this patch? Taken from CVS. Have fun,
Perfect! :-)
Thanks a lot,
Zack
--
Zack Brown
prev parent reply other threads:[~2003-04-14 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 10:49 lk-changelog.pl 0.96 Matthias Andree
2003-04-13 14:42 ` Zack Brown
2003-04-13 16:23 ` Matthias Andree
2003-04-13 17:09 ` Zack Brown
2003-04-14 15:49 ` Matthias Andree
2003-04-14 16:29 ` Zack Brown [this message]
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=20030414162919.GQ2091@renegade \
--to=zbrown@tumblerings.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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.
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).