From: Lars Wendler <polynomial-c@gentoo.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Herd likely up for grabs: kernel-misc
Date: Thu, 21 Jan 2016 13:56:21 +0100 [thread overview]
Message-ID: <20160121135621.02e92dfe@shanghai.paradoxon.rec> (raw)
In-Reply-To: <20160120184004.GA14840@vapier.lan>
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
Hi guys,
On Wed, 20 Jan 2016 13:40:04 -0500 Mike Frysinger wrote:
>On 20 Jan 2016 12:39, Rich Freeman wrote:
>> On Wed, Jan 20, 2016 at 12:34 PM, Mike Frysinger <vapier@gentoo.org>
>> wrote:
>> > On 18 Jan 2016 00:57, Joshua Kinard wrote:
>> >> On 01/17/2016 14:57, Michał Górny wrote:
>> >> > sys-apps/kexec-tools :
>> >>
>> >> Better suited for base-system, maybe?
>> >>
>> >> > sys-fs/jfsutils :
>> >>
>> >> Definitely base-system, as xfsprogs is already maintained by
>> >> them.
>> >
>> > sounds fine for both. generally fs tools probably should live
>> > under base-system for consistency.
>>
>> Nothing wrong with consistency, but I'd prefer a package to be placed
>> under the base-system project because the base-system project members
>> intend to maintain it. I don't want to see packages placed into
>> projects simply because they're similar to other packages in those
>> projects if it means they'll just be neglected.
>>
>> I have no idea which is the case here. If the base-system
>> maintainers want to maintain these two packages, have at it! If
>> not, leave it as maintainer-needed.
>
>if base-system@ isn't going to maintain it, we'll punt it from the herd
>-mike
well, I already added myself as maintainer of sys-fs/jfsutils and I
happen to be a base-system maintainer. So goal already reached :)
Kind regards
Lars
--
Lars Wendler
Gentoo package maintainer
GPG: 21CC CF02 4586 0A07 ED93 9F68 498F E765 960E 9B39
Attention! New gpg key! See (self signed server cert for now)
http://www.gentoofan.org/blog/index.php?/archives/9-New-gpg-keys.html
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-21 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 19:57 [gentoo-dev] Herd likely up for grabs: kernel-misc Michał Górny
2016-01-17 22:54 ` Lars Wendler
2016-01-18 5:57 ` Joshua Kinard
2016-01-20 17:34 ` Mike Frysinger
2016-01-20 17:39 ` Rich Freeman
2016-01-20 18:40 ` Mike Frysinger
2016-01-20 19:48 ` [gentoo-dev] " Duncan
2016-01-20 20:26 ` Rich Freeman
2016-01-21 6:06 ` Mike Frysinger
2016-01-21 11:55 ` Rich Freeman
2016-01-22 12:00 ` Joshua Kinard
2016-01-21 12:56 ` Lars Wendler [this message]
2016-01-22 4:59 ` [gentoo-dev] " Michał Górny
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=20160121135621.02e92dfe@shanghai.paradoxon.rec \
--to=polynomial-c@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=vapier@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