lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 26 Feb 2017 11:37:04 -0800
From:   Joe Perches <joe@...ches.com>
To:     Julia Lawall <julia.lawall@...6.fr>
Cc:     Narcisa Ana Maria Vasile <narcisaanamaria12@...il.com>,
        swarren@...dotorg.org, lee@...nel.org, eric@...olt.net,
        f.fainelli@...il.com, rjui@...adcom.com, sbranden@...adcom.com,
        daniel.baluta@...mfreegmail.com, gregkh@...uxfoundation.org,
        outreachy-kernel@...glegroups.com,
        bcm-kernel-feedback-list@...adcom.com, mzoran@...wfest.net,
        danielperezdeandres@...il.com, dan.carpenter@...cle.com,
        devel@...verdev.osuosl.org, linux-rpi-kernel@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed
 spacing around '&'

On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote:
> On Sun, 26 Feb 2017, Joe Perches wrote:
> > Mailing lists _should_ be copied on patch submissions.
> 
> The idea of outreachy is that it should be a place for people to get
> started without too much criticism from the outside.  Originally, only the
> outreachy mailing list received patches.  But staging maintainers were
> confused to have their drivers receiving patches that they had not seen.
> So we expanded it to maintainers.

That also doesn't make much sense as patches
should not be applied that have not reached
a mailing list for review.

As long as initial outreachy patches are not
applied and are just for internal review by
any outside person but the outreachy list and
are not be applied by maintainers, then perhaps
it's best if neither maintainers nor lists are
cc'd on the patches.

And the link you sent is for newbies, not for
outreachy.

The "don't cc lists" --nol use is inappropriate
there.

Powered by blists - more mailing lists