From: Mark Loeser <halcy0n@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites for dev-util/cccc
Date: Sat, 15 Apr 2006 12:07:34 -0400 [thread overview]
Message-ID: <20060415160734.GE18636@aerie.halcy0n.com> (raw)
In-Reply-To: <1145098556.17585.2.camel@rivendell>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
foser <foser@gentoo.org> said:
> On Sat, 2006-04-15 at 02:54 -0400, Mike Frysinger wrote:
> > cccc-3.1.4 now in portage
>
> Why did you add that, without adding metadata ? That is just wrong.
>
> It is better to remove it if there is no maintainer, you upping it
> without adding yourself as maintainer is no form of maintenance. This is
> exactly why we get complaints about a stale tree.
>
> I still say it should be removed in 30 days.
I agree. There is a lot of stuff that suffers from being unmaintained,
and I think we should strive towards cleaning that up. It helps no one
if there isn't anyone to claim responsibility for the package when there
is a problem.
Just my 2 cents,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-15 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 4:49 [gentoo-dev] Last rites for dev-util/cccc Mark Loeser
2006-04-15 6:54 ` Mike Frysinger
2006-04-15 10:55 ` foser
2006-04-15 16:07 ` Mark Loeser [this message]
2006-04-15 17:46 ` Chris Bainbridge
2006-04-15 18:24 ` Mike Frysinger
2006-04-16 15:17 ` foser
2006-04-16 20:42 ` Mike Frysinger
2006-04-18 11:00 ` foser
2006-04-18 13:11 ` Chris Bainbridge
2006-04-18 13:51 ` foser
2006-04-18 14:22 ` Mike Frysinger
2006-04-18 14:41 ` foser
2006-04-18 14:53 ` Mike Frysinger
2006-04-18 15:13 ` foser
2006-04-18 14:56 ` Philippe Trottier
2006-04-18 15:16 ` foser
2006-04-18 16:13 ` Philippe Trottier
2006-04-18 14:21 ` Mike Frysinger
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=20060415160734.GE18636@aerie.halcy0n.com \
--to=halcy0n@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