[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgCp5n3sB_hDmOLSPiJcwJm9RErBHN_6ABhRWyVEkY4Xw@mail.gmail.com>
Date: Sun, 14 Feb 2021 11:57:57 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Pavel Machek <pavel@....cz>
Cc: kernel list <linux-kernel@...r.kernel.org>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Linux LED Subsystem <linux-leds@...r.kernel.org>
Subject: Re: [GIT PULL 5.11-rc8] LED fix
On Sun, Feb 14, 2021 at 9:13 AM Pavel Machek <pavel@....cz> wrote:
>
> Unfortunately, for some reason request-pull is not willing to
> cooperate, so I'm just doing this manually.
The reason request-pull doesn't cooperate is actually spelled out explicitly:
> pavel@duo:/data/l/linux-leds$ git request-pull master git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git/ 92bf22614b21a2706f4993b278017e437f7785b3 > /tmp/delme for-rc8-5.11
> warn: No match for commit 92bf22614b21a2706f4993b278017e437f7785b3 found at git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git/
> warn: Are you sure you pushed '92bf22614b21a2706f4993b278017e437f7785b3' there?
Commit 92bf22614b21 is my rc7 commit. And it's not in your tree (which
is based on rc1).
Why are you giving raw commit ID's to git request-pull? Particularly
ones that aren't even in your upstream tree? Git figures things out on
its own, why do you point to the rc7 commit that has nothing to do
with what you're pushing?
And yes, that commit exists on kernel.org through my tree, but it's
not reachable from any tips in yours (because your work was based on
earlier state - which is as it should be).
Linus
Powered by blists - more mailing lists