From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Automated Package Removal and Addition Tracker, for the week ending 2006-12-17 23:59 UTC
Date: Wed, 20 Dec 2006 05:04:50 +0000 [thread overview]
Message-ID: <emag6t$6gq$2@sea.gmane.org> (raw)
In-Reply-To: 1166468672.11642.18.camel@inertia.twi-31o2.org
Chris Gianelloni wrote:
> On Mon, 2006-12-18 at 11:38 -0500, Alec Warner wrote:
>> The only reason the contact and date are there is because the code for
>> removals and additions is basically the same (A or D tells me which one
>> it is) and all that info is available in the CVS history file. The
>> problem with HOMEPAGE or DESCRIPTION is that they are version specific
>> and there is no way to choose which version to pick in the case where
>> more than one version was added at the same time.
>
> As a compromise, how about having the package names link to their
> packages.gentoo.org page?
>
That'd be much better as then we'd be able to check the bugs as well.
There's some other semi-official gentoo site that produces those details,
but not the bugs..
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-12-20 5:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 7:20 [gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2006-12-17 23:59 UTC Robin H. Johnson
2006-12-18 7:35 ` Robin H. Johnson
2006-12-18 13:47 ` Chris Gianelloni
2006-12-18 14:13 ` Chris Gianelloni
2006-12-18 14:51 ` [gentoo-dev] New packages, but why? Chris Gianelloni
2006-12-18 15:02 ` [gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2006-12-17 23:59 UTC Chris Gianelloni
2006-12-18 15:33 ` Yuri Vasilevski
2006-12-18 16:38 ` Alec Warner
2006-12-18 19:04 ` Chris Gianelloni
2006-12-20 5:04 ` Steve Long [this message]
2006-12-18 20:53 ` Yuri Vasilevski
2006-12-18 21:28 ` Robin H. Johnson
2006-12-18 22:52 ` Yuri Vasilevski
2006-12-18 19:15 ` Robin H. Johnson
2006-12-18 20:11 ` Philip Webb
2006-12-18 19:14 ` Robin H. Johnson
2006-12-30 19:15 ` Paul de Vrieze
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='emag6t$6gq$2@sea.gmane.org' \
--to=slong@rathaus.eclipse.co.uk \
--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