From: Linus Torvalds <torvalds@linux-foundation.org>
To: Johannes Thumshirn <johannes.thumshirn@men.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Borislav Petkov <bp@suse.de>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
Robert Richter <rric@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-edac@vger.kernel.org
Subject: Re: [GIT PULL] mpc85xx_edac changes for 3.13
Date: Thu, 14 Nov 2013 14:41:24 +0900 [thread overview]
Message-ID: <CA+55aFzJhyo8bKBchYq0Q=rwPv_-v-xWgOKWxKBcSBycMZcmTg@mail.gmail.com> (raw)
In-Reply-To: <20131112161901.GA15637@jtlinux>
On Wed, Nov 13, 2013 at 1:19 AM, Johannes Thumshirn
<johannes.thumshirn@men.de> wrote:
>
> git://github.com/morbidrsa/linux.git tags/mpc85xx-edac-for-3.13
Ok, it's a signed tag, but I haven't pulled from you before (all the
commits I see seem to have gone through Greg), and I don't recognize
any of the signatures on your tag.
That, together with not really knowing the whole edac area, makes me
not wonderfully happy about pulling directly. I a.lso see another edac
pull request in my mailbox, making me suspect that there are
maintainership problems (historically I've been getting the code
either though Greg, Borislav or Mauro). So I'd also like to make sure
that I at least _know_ about any disputes going on in this area?
So before I pull this, I'd quickly like to validate the gpg key, and
am cc'ing more people to see if I'm stepping into some political
nightmare. I can be ok with that, but I want to do so knowingly, not
blindly..
Linus
next prev parent reply other threads:[~2013-11-14 5:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 16:19 [GIT PULL] mpc85xx_edac changes for 3.13 Johannes Thumshirn
2013-11-14 5:41 ` Linus Torvalds [this message]
2013-11-14 5:47 ` Greg Kroah-Hartman
2013-11-14 9:20 ` Borislav Petkov
2013-11-14 11:18 ` Mauro Carvalho Chehab
2013-11-14 11:24 ` Borislav Petkov
2013-11-14 12:13 ` Robert Richter
2013-11-14 14:21 ` Johannes Thumshirn
2013-11-14 17:08 ` Mauro Carvalho Chehab
2013-11-14 18:30 ` Borislav Petkov
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+55aFzJhyo8bKBchYq0Q=rwPv_-v-xWgOKWxKBcSBycMZcmTg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=bp@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=johannes.thumshirn@men.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=rric@kernel.org \
/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.