From: Rob Cakebread <pythonhead@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] List of aging ebuilds?
Date: Sat, 18 Jun 2005 14:09:27 -0700 [thread overview]
Message-ID: <42B48D87.1050002@gentoo.org> (raw)
In-Reply-To: <C068892A-849C-45C1-B2BB-C2649A4FB68B@gentoo.org>
Hasan Khalil wrote:
> If this is of any interest to anyone out there, let me know. As always,
> I'm open to discussion and suggestions.
>
> [1] http://charlies-server.no-ip.com/~gongloo/keywordlog
>
Great, thats just about what I'm looking for. I wasn't as interested in
the repoman top 10 stuff. Mainly I want to be able to search by the
herds I'm in to get a quick glance at anything stuck at ~arch for
>30 days.
--
Rob Cakebread
Gentoo Linux Developer
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x96BA679B
Key fingerprint = 5E1A 57A0 0FA6 939D 3258 8369 81C5 A17B 96BA 679B
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2005-06-18 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 16:14 [gentoo-dev] List of aging ebuilds? Rob Cakebread
2005-06-17 10:32 ` Markus Nigbur
2005-06-17 13:30 ` Lance Albertson
2005-06-18 12:39 ` [gentoo-dev] " Duncan
2005-06-19 0:20 ` Andrej Kacian
2005-06-18 18:38 ` [gentoo-dev] " Hasan Khalil
2005-06-18 21:09 ` Rob Cakebread [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=42B48D87.1050002@gentoo.org \
--to=pythonhead@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