All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
	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 19:08:42 +0100	[thread overview]
Message-ID: <20181115180842.GD25056@zn.tnic> (raw)
In-Reply-To: <20181115172706.GA229449@google.com>

On Thu, Nov 15, 2018 at 11:27:06AM -0600, Bjorn Helgaas wrote:
> 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.

So what I've done here is I've added a remote git repo using the
*public* URL of my repo and so when I use git request-pull, I always
point to the public one - I need to fetch the tag before, of course, but
that's trivial - and then the URL is the public one.

I.e,

$ git request-pull master bp-pub <TAG>

This has the additional value of *actually* making sure I've really
pushed the tag.

HTH.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  reply	other threads:[~2018-11-15 18:08 UTC|newest]

Thread overview: 20+ 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
2018-11-15 18:08                       ` Borislav Petkov [this message]
2018-11-15 18:13                       ` Konstantin Ryabitsev
  -- strict thread matches above, loose matches on Subject: below --
2018-12-01  5:59 Bjorn Helgaas
2018-12-01 20:05 ` pr-tracker-bot
2018-12-07 20:44 Bjorn Helgaas
2018-12-07 21:10 ` pr-tracker-bot
2018-12-18 21:40 Bjorn Helgaas
2018-12-18 23:55 ` pr-tracker-bot

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=20181115180842.GD25056@zn.tnic \
    --to=bp@alien8.de \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=gregkh@linuxfoundation.org \
    --cc=helgaas@kernel.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 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.