Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1368768

Re: [git pull] orangefs bugfixes for rc2

From Mike Marshall <hubcap@omnibond.com>
Newsgroups linux.kernel
Subject Re: [git pull] orangefs bugfixes for rc2
Date 2016-03-31 23:10 +0200
Message-ID <riS0Q-2t5-53@gated-at.bofh.it> (permalink)
References <riNua-7Ia-5@gated-at.bofh.it> <riQs1-1gf-7@gated-at.bofh.it> <riS0Q-2t5-49@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


sorry to follow up my own post... perhaps we should
point our pull requests at Al and base them on one
of Al's trees? I'm sure all this should be easy, we're
just clumsy 'cause we're new...

-Mike

On Thu, Mar 31, 2016 at 5:01 PM, Mike Marshall <hubcap@omnibond.com> wrote:
> 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@linux-foundation.org> wrote:
>> 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

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[git pull] orangefs bugfixes for rc2 Martin Brandenburg <martin@omnibond.com> - 2016-03-31 18:20 +0200
  Re: [git pull] orangefs bugfixes for rc2 Linus Torvalds <torvalds@linux-foundation.org> - 2016-03-31 21:30 +0200
    Re: [git pull] orangefs bugfixes for rc2 Mike Marshall <hubcap@omnibond.com> - 2016-03-31 23:10 +0200
      Re: [git pull] orangefs bugfixes for rc2 Mike Marshall <hubcap@omnibond.com> - 2016-03-31 23:10 +0200
        Re: [git pull] orangefs bugfixes for rc2 Linus Torvalds <torvalds@linux-foundation.org> - 2016-04-01 00:20 +0200
        Re: [git pull] orangefs bugfixes for rc2 Al Viro <viro@ZenIV.linux.org.uk> - 2016-04-01 01:00 +0200
      Re: [git pull] orangefs bugfixes for rc2 Theodore Ts'o <tytso@mit.edu> - 2016-04-01 03:30 +0200
    Re: [git pull] orangefs bugfixes for rc2 Martin Brandenburg <martin@omnibond.com> - 2016-04-01 22:00 +0200
      Re: [git pull] orangefs bugfixes for rc2 Linus Torvalds <torvalds@linux-foundation.org> - 2016-04-02 00:40 +0200
        Re: [git pull] orangefs bugfixes for rc2 Mike Marshall <hubcap@omnibond.com> - 2016-04-02 01:30 +0200
      Re: [git pull] orangefs bugfixes for rc2 Joe Perches <joe@perches.com> - 2016-04-02 01:30 +0200
        Re: [git pull] orangefs bugfixes for rc2 Martin Brandenburg <martin@omnibond.com> - 2016-04-02 03:40 +0200

csiph-web