Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933378AbcCaVBw (ORCPT ); Thu, 31 Mar 2016 17:01:52 -0400 Received: from mail-lf0-f42.google.com ([209.85.215.42]:36681 "EHLO mail-lf0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933264AbcCaVBt (ORCPT ); Thu, 31 Mar 2016 17:01:49 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 31 Mar 2016 17:01:47 -0400 Message-ID: Subject: Re: [git pull] orangefs bugfixes for rc2 From: Mike Marshall To: Linus Torvalds Cc: Martin Brandenburg , Al Viro , Linux Kernel Mailing List , linux-fsdevel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1425 Lines: 42 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 wrote: > On Thu, Mar 31, 2016 at 11:17 AM, Martin Brandenburg > 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