From: Eldad Zack <eldad@gentoo.org>
To: Gentoo-Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Package notices
Date: Sat, 04 Sep 2004 15:55:23 +0300 [thread overview]
Message-ID: <1094302523.7135.2.camel@localhost> (raw)
In-Reply-To: <20040903051038.GA11426@twobit.net>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
On Fri, 2004-09-03 at 08:10, Nicholas Jones wrote:
> If you are so inclined, you could also write a parser for
> these files that can designate priorities using color or
> some other visual aid. (Keep in mind that it must be
> deterministic through simple ascii as well for synthesisers.)
> For multiple reasons, I prefer python for these tools.
I've whipped up a tool to do just that.
It can be found along the patch (which was slightly amended), on my
page:
http://dev.gentoo.org/~eldad/ebuild.sh-enotice.patch
http://dev.gentoo.org/~eldad/enotice
Comments?
--
Eldad Zack <eldad@gentoo.org>
Key/Fingerprint at pgp.mit.edu, ID 0x96EA0A93
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-04 12:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 20:12 [Fwd: Re: [gentoo-dev] Package notices] Eldad Zack
2004-09-02 22:17 ` Chris Gianelloni
2004-09-02 22:54 ` Thomas de Grenier de Latour
2004-09-03 5:10 ` [gentoo-dev] Package notices Nicholas Jones
2004-09-03 14:00 ` Pablo Villalba
2004-09-03 12:47 ` Jason Stubbs
2004-09-03 15:10 ` Eldad Zack
2004-09-03 14:15 ` Jason Stubbs
2004-09-03 16:15 ` Eldad Zack
2004-09-04 12:55 ` Eldad Zack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-01 19:42 Eldad Zack
2004-09-01 21:05 ` William Hubbs
2004-09-01 22:01 ` Thomas de Grenier de Latour
2004-09-02 16:46 ` purslow
2004-09-02 18:06 ` Anton Starikov
2004-09-02 19:59 ` N. Owen Gunden
2004-09-02 18:46 ` Christian Gut
2004-09-02 18:56 ` Alexander Gretencord
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=1094302523.7135.2.camel@localhost \
--to=eldad@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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