From: "Anthony G. Basile" <basile@opensource.dyc.edu>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] [PATCH] sys-libs/pam: Fixed building under musl using patchset from Alpine Linux -- this time in an attachment
Date: Mon, 23 Feb 2015 08:10:27 -0500 [thread overview]
Message-ID: <54EB26C3.7040905@opensource.dyc.edu> (raw)
In-Reply-To: <54EB1C3C.8010403@opensource.dyc.edu>
On 02/23/15 07:25, Anthony G. Basile wrote:
> On 02/20/15 21:10, Alex Efros wrote:
>> Hi!
>>
>> On Sat, Feb 21, 2015 at 12:45:57AM +1100, James Taylor wrote:
>>> Not sure if there is any preferred method for sending patches, but
>>> here's a second attempt with an attachment :)
>>
>> I'm afraid any patches in maillist will be ignored, please use
>> https://bugs.gentoo.org/
>>
>
> Um, no they are not! There are lots of mailing lists which are
> specifically for patches.
>
> But since these are for musl, its best to email them to me directly:
> blueness@gentoo.org.
>
> James, thanks for the patches.
>
James, I applied these.
Not to embarrass you Alex, but think about the situation these
contributors are in:
1) if the post to bugzilla they're told not to because the patches are
for an overlay. also patches for the tree should be absolutely minimal
to show the issue while for hte overlay i just want the full shebang so
I can just conveniently apply. Furthermore in bugzilla, they can't
assign the bugs to me directly and the maintainers of packages get
annoyed wondering what is this stuff.
2) if they email here they're told its not appropriate either because
its a patch or because its musl and not hardened etc. I'd bother infra
for a new list and/or repo but they're overworked.
add to this the fact that I often have to give advice on how to format
these patches and contributors get frustrated and they loose enthusiasm
for the project.
Soo .... as a word to contributers. If your contributing musl patches,
email them directly to me: blueness@gentoo.org. If you simultaneously
want to get the stuff into the tree and that is definitely our goal,
then open a bug on bugzilla and submit just a very minimal patch there.
Say in comment 0 to cc me as the musl maintainer.
Thanks again!
--
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197
prev parent reply other threads:[~2015-02-23 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 13:45 [gentoo-hardened] [PATCH] sys-libs/pam: Fixed building under musl using patchset from Alpine Linux -- this time in an attachment James Taylor
2015-02-21 2:10 ` Alex Efros
2015-02-23 12:25 ` Anthony G. Basile
2015-02-23 13:10 ` Anthony G. Basile [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=54EB26C3.7040905@opensource.dyc.edu \
--to=basile@opensource.dyc.edu \
--cc=gentoo-hardened@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