linux-kernel - Re: [git pull] orangefs bugfixes for rc2

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 linux-hardening linux-cve-announce 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:	Thu, 31 Mar 2016 17:01:47 -0400
From:	Mike Marshall <hubcap@...ibond.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Martin Brandenburg <martin@...ibond.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [git pull] orangefs bugfixes for rc2

Hi everyone...

I'm at the Linux Foundation meeting at Tahoe, I've been
asking around some, I know we need to do things differently
now that we are upstream... there's several things in my mailbox
besides what Martin has done that need to go up...

I think we need, during the rc period, to post our patches here
in case anyone wants to look at them, put them in our for-next
branch so that all the robots can test them, and then after
a week or so post a pull request similar to Martin's for them,
but from our kernel.org tree... pull requests for reviewed code
from kernel.org doesn't need signed tags...

Does that sound mostly right?

-Mike

On Thu, Mar 31, 2016 at 3:27 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Thu, Mar 31, 2016 at 11:17 AM, Martin Brandenburg
> <martin@...ibond.com> wrote:
>>
>> Please pull two bugfixes for OrangeFS.
>
> I *really* want signed tags when pulling from github or similar open
> hosting sites.
>
> So can you please re-do the pull request, but rather than just a plain
> branch, use
>
>   "git tag -s"
>
> to create a signed tag for me to pull?
>
> Even if your key doesn't end up being connected to other kernel
> developers (I have no idea), I'll be able to see that I'm pulling from
> the same person, and presumably you and Mike can sign (or already have
> signed) each others keys etc so that eventually that connection is
> visible too.
>
>             Linus