From: Eldad Zack <eldad@gentoo.org>
To: Gentoo-Dev <gentoo-dev@lists.gentoo.org>
Subject: [Fwd: Re: [gentoo-dev] aging ebuilds with unstable keywords]
Date: Wed, 14 Jul 2004 23:27:55 +0300 [thread overview]
Message-ID: <1089836874.24444.5.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
[hrrrmmrm reply to all]
-----Forwarded Message-----
From: Eldad Zack <eldad@gentoo.org>
To: Matthias Liertzer <linux@liertzer.at>
Subject: Re: [gentoo-dev] aging ebuilds with unstable keywords
Date: Wed, 14 Jul 2004 23:26:19 +0300
On Wed, 2004-07-14 at 21:24, Matthias Liertzer wrote:
> > app-office/gnofin-0.8.4 - 892 days (~amd64)
> > app-office/sc-7.12 - 892 days (~amd64)
> > x11-misc/e16keyedit-0.2 - 892 days (~amd64)
> > x11-misc/xkeycaps-2.46 - 892 days (~amd64)
>
> hmm, AFAIK amd64 doesn't even exist for such a long time, so i guess there's a
> mistake in your script
No mistake.
adding keywords along the way is not logged (unlike version bumps) - the
script can only count the number of days since the ebuild was introduced
until today.
--
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 --]
reply other threads:[~2004-07-14 20:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1089836874.24444.5.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