All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Martin Brandenburg <martin@omnibond.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	Mike Marshall <hubcap@omnibond.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [git pull] orangefs bugfixes for rc2
Date: Thu, 31 Mar 2016 14:27:31 -0500	[thread overview]
Message-ID: <CA+55aFzRDqVaFw0mpHS5_VsyjP+b8KiLTP+a2opgDKOsLHCTLA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSO.2.20.1603311208110.15868@server1.sysblue.org>

On Thu, Mar 31, 2016 at 11:17 AM, Martin Brandenburg
<martin@omnibond.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

  reply	other threads:[~2016-03-31 19:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31 16:17 [git pull] orangefs bugfixes for rc2 Martin Brandenburg
2016-03-31 19:27 ` Linus Torvalds [this message]
2016-03-31 21:01   ` Mike Marshall
2016-03-31 21:06     ` Mike Marshall
2016-03-31 22:11       ` Linus Torvalds
2016-03-31 22:59       ` Al Viro
2016-04-01  1:19     ` Theodore Ts'o
2016-04-01 19:49   ` Martin Brandenburg
2016-04-01 22:35     ` Linus Torvalds
2016-04-01 23:29       ` Mike Marshall
2016-04-01 23:23     ` Joe Perches
2016-04-02  1:32       ` Martin Brandenburg

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=CA+55aFzRDqVaFw0mpHS5_VsyjP+b8KiLTP+a2opgDKOsLHCTLA@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=hubcap@omnibond.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@omnibond.com \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.