From: foser <foser@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites for dev-util/cccc
Date: Tue, 18 Apr 2006 15:51:43 +0200 [thread overview]
Message-ID: <1145368303.18478.27.camel@rivendell> (raw)
In-Reply-To: <623652d50604180611h424db1e1tca69de0409c8be2a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
On Tue, 2006-04-18 at 14:11 +0100, Chris Bainbridge wrote:
> Are you suggesting that all packages with long standing open bug
> reports should be removed? There are thousands that fit that
> description. If not, then what is your definition of "maintained"? It
> could be argued that since Mike fixed the cccc bug, it is maintained,
> even though he isn't the maintainer. Likewise, there are hundreds of
> packages that have a maintainer listed, or are assigned to a herd,
> where bug reports are essentially ignored. Should those also be
> removed?
No, I don't know why you jump to that conclusion. There are people
responsible there, you can contact them if you feel things are ignored.
Or better, you can try and help out on those outstanding bugs and solve
them, so the maintainers would only need to apply a fix.
> Did you read the previous discussion link I provided? The argument has
> been rejected in the past because it would lead to hundreds of
> otherwise working packages being removed.
You get a lot more out of that thread than I do, I guess it's a matter
of interpretation.
> Maybe you aren't a native English speaker; it was clear from Mike's
> post that he would rather you didn't go ahead with removing hundreds
> of packages.
I don't know how this relates to my mother tongue, but I'm not speaking
of a mass removal or anything. You make it into that all the time, maybe
you should let go of that mindset. I think that if we come across cases
like this the goal should be to clear up the confusion. Either find a
maintainer or clean it out. That way eventually 'hundreds' becomes
'dozens' of unmaintained packages and maybe some day even less, it's a
gradual process.
- foser
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-04-18 13:54 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
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 [this message]
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=1145368303.18478.27.camel@rivendell \
--to=foser@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