From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Removals reply - please write adequate log messages!
Date: Sat, 2 Feb 2013 20:35:14 +0100 [thread overview]
Message-ID: <201302022035.14415.dilfridge@gentoo.org> (raw)
In-Reply-To: <CA+Nrkpd2E6KQQOt6FEN9eVdzcw9kpr06gbzUBOcFSj5rPbKPXw@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1000 bytes --]
Am Freitag, 1. Februar 2013, 14:53:19 schrieb Tomáš Chvátal:
> just to be sure here "Removals are completely up to the maintainer to
> decide", with expection of QA removal where the package must be
> already broken to get punted.
>
> If you as developers and users find some package useful you can retake
> the maintainership (or became proxy-maint) which also expects you to
> take care of the bugs (QA can prune it even if you take the
> maintainership but ignore failures [even if your personal feeling is
> that it is corner case, it is for QA to deicde]).
I agree 100% that we should not accumulate cruft in the tree and that removals
are necessary. Please however,
*** write meaningful log or mask messages *** !!!
"Old and uses IMake" is not really a reason for treecleaning. "Fortify crash
on start and unuseable on fast machines" definitely is.
Cheers, A
--
Andreas K. Huettel
Gentoo Linux developer
dilfridge@gentoo.org
http://www.akhuettel.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-02-02 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 13:53 [gentoo-dev] Removals reply (I am not going to figure out which tread of those all should i reply to) Tomáš Chvátal
2013-02-01 14:52 ` Rich Freeman
2013-02-01 17:00 ` Tomáš Chvátal
2013-02-01 17:05 ` Diego Elio Pettenò
2013-02-02 19:35 ` Andreas K. Huettel [this message]
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=201302022035.14415.dilfridge@gentoo.org \
--to=dilfridge@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