From: "Chris Bainbridge" <chris.bainbridge@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites for dev-util/cccc
Date: Tue, 18 Apr 2006 14:11:50 +0100 [thread overview]
Message-ID: <623652d50604180611h424db1e1tca69de0409c8be2a@mail.gmail.com> (raw)
In-Reply-To: <1145358044.18478.11.camel@rivendell>
On 18/04/06, foser <foser@gentoo.org> wrote:
> On Sun, 2006-04-16 at 16:42 -0400, Mike Frysinger wrote:
> > well the logical thing would be to go to bugzilla and search for "cccc" ...
> > and guess what ? no more open bug reports
>
> I already did that when I wrote it, actually there still is an open bug
> for it. So I guess you didn't actually go trough these proposed steps
> yourself. Anyway, it is completely besides the point, because you or
> anyone else won't check a week or a month from now if there's bug filed
> against cccc, that is what maintenance is about.
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?
> > > I mean, you aren't the maintainer. And there is still the outstanding
> > > issue that it is unmaintained in Gentoo, are you going to fix that or
> > > not ? Otherwise it should be masked and removed.
> >
> > this is the same argument as already made and rejected ...
>
> Where was this rejected and by whom ? By you I guess ? That just doesn't
> cut it, errors made in the past are no reason to make them again in the
> future.
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.
> > feel free to mask
> > and remove the hundreds of other packages that have no maintainer
>
> So now we do have your blessing ? cccc is then up for removal as of this
> moment.
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.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-18 13:13 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 [this message]
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=623652d50604180611h424db1e1tca69de0409c8be2a@mail.gmail.com \
--to=chris.bainbridge@gmail.com \
--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