From: Bjorn Helgaas <helgaas@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "Borislav Petkov" <bp@alien8.de>,
pr-tracker-bot@kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Thomas Lendacky" <Thomas.Lendacky@amd.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Martin Hundebøll" <martin@geanix.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Len Brown" <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [GIT PULL] PCI fixes for v4.20
Date: Thu, 15 Nov 2018 11:27:06 -0600 [thread overview]
Message-ID: <20181115172706.GA229449@google.com> (raw)
In-Reply-To: <20181115155418.GA25764@pure.paranoia.local>
On Thu, Nov 15, 2018 at 10:54:18AM -0500, Konstantin Ryabitsev wrote:
> On Thu, Nov 15, 2018 at 09:03:21AM -0600, Bjorn Helgaas wrote:
> > > You didn't really do anything wrong. In *general* I prefer to see
> > > public URLs if they are sent to public lists, so if you're cc'ing
> > > something to LKML, I would generally expect the pull request to have a
> > > public URL like https://git.kernel.org/ instead of a private ssh:// URL
> > > that is only accessible to people with a kernel.org account.
> > >
> > > That's basically all there is to it. It doesn't *really* matter, since
> > > Linus is the one who will be merging the actual pull request, and he
> > > certainly has access to internal ssh:// URLs. However, in case someone
> > > else was interested in reviewing the pull request, it would be more
> > > friendly to have a public URL for them.
> >
> > OK, I think I'll remove the insteadOf chunk from my .gitconfig. Should
> > https://korg.wiki.kernel.org/userdoc/gitolite be updated to remove or
> > expand that recommendation? The only reason I added insteadOf in the first
> > place was because it sounded like a security improvement.
>
> It is. Does adding the insteadOf rules result in ssh:// URLs when using
> git-request-pull? I didn't expect that it would.
Yep, it seems to for me. Maybe I'm doing something else weird, because I
don't see many other pull requests with ssh:// URLs.
next prev parent reply other threads:[~2018-11-15 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 6:20 [GIT PULL] PCI fixes for v4.20 Bjorn Helgaas
2018-11-14 20:00 ` pr-tracker-bot
2018-11-14 20:12 ` Borislav Petkov
2018-11-14 20:16 ` Konstantin Ryabitsev
2018-11-14 21:46 ` Borislav Petkov
2018-11-14 22:21 ` Konstantin Ryabitsev
2018-11-14 22:48 ` Borislav Petkov
2018-11-15 7:12 ` Bjorn Helgaas
2018-11-15 7:53 ` Konstantin Ryabitsev
2018-11-15 15:03 ` Bjorn Helgaas
2018-11-15 15:54 ` Konstantin Ryabitsev
2018-11-15 17:27 ` Bjorn Helgaas [this message]
2018-11-15 18:08 ` Borislav Petkov
2018-11-15 18:13 ` Konstantin Ryabitsev
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=20181115172706.GA229449@google.com \
--to=helgaas@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=Thomas.Lendacky@amd.com \
--cc=a.p.zijlstra@chello.nl \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=martin@geanix.com \
--cc=mingo@kernel.org \
--cc=pr-tracker-bot@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).