linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: pr-tracker-bot@kernel.org, Guo Ren <guoren@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	linux-arch <linux-arch@vger.kernel.org>
Subject: Re: [GIT PULL] csky fixup for linux-5.0-rc1
Date: Wed, 9 Jan 2019 15:05:21 -0500	[thread overview]
Message-ID: <20190109200521.GE30131@pure.paranoia.local> (raw)
In-Reply-To: <CAHk-=wi-4DfZDM2xE2qDnj0acEfgfW5wPWxcps-V5XD8TNAw5w@mail.gmail.com>

On Wed, Jan 09, 2019 at 10:40:20AM -0800, Linus Torvalds wrote:
> Side note: I do wish people would use the proper _public_ access.

I'm wondering if this largely happens due to people's insteadOf rules.
We've established that git-request-pull will quietly substitute URLs in
the emails it generates if a matching insteadOf rule is found. I started
a discussion related to this on the git list, but it veered a bit
sideways:

https://public-inbox.org/git/20181115182826.GB25806@pure.paranoia.local/T/#u

> Maybe the pr-tracker-bot might even send the person who did a pull
> request a (private) notice that there is something odd when that isn't
> the case?

I'm not sure that would be very effective. Folks tend to ignore bots,
and with this one we're specifically recommending "add it to your ignore
list if you don't want notifications." I think an email from you for
such (rare) cases would be a better way to indicate that something in
the pull request needs to be changed.

-K


  reply	other threads:[~2019-01-09 20:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 14:49 [GIT PULL] csky fixup for linux-5.0-rc1 guoren
2019-01-09 18:05 ` pr-tracker-bot
2019-01-09 18:29   ` Konstantin Ryabitsev
2019-01-09 18:40     ` Linus Torvalds
2019-01-09 20:05       ` Konstantin Ryabitsev [this message]
2019-01-10  8:02     ` Guo Ren
2019-01-10 13:26       ` Konstantin Ryabitsev
2019-01-10 13:29         ` Guo Ren
2019-01-10  8:10 ` Guo Ren
2019-01-10 11:22   ` Arnd Bergmann
2019-01-10 12:33     ` Guo Ren
2019-01-10 11:59   ` Linus Torvalds
2019-01-10 12:35     ` Guo Ren

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=20190109200521.GE30131@pure.paranoia.local \
    --to=konstantin@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=guoren@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pr-tracker-bot@kernel.org \
    --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).