From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konstantin Ryabitsev Subject: Re: [GIT PULL] Thermal-SoC management fixes for v5.0-rc6 Date: Mon, 11 Feb 2019 18:10:16 -0500 Message-ID: <20190211231016.GA2937@chatter.qube.local> References: <20190210041721.GA2805@localhost.localdomain> <154977271617.2362.11794417398216386913.pr-tracker-bot@kernel.org> <20190211031921.GA1799@localhost.localdomain> <20190211201619.GA8065@work> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Linus Torvalds Cc: Eduardo Valentin , pr-tracker-bot@kernel.org, Rui Zhang , ACPI Devel Maling List , Linux PM , LKML List-Id: linux-acpi@vger.kernel.org On Mon, Feb 11, 2019 at 02:04:08PM -0800, Linus Torvalds wrote: >> Okay, so I need guidance on the proper behaviour here. As this >> request >> didn't use the magic wording for the commit-id (as generated by >> git-request-pull), we ended up trying to look up the remote. The remote >> specified was: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal fixes >> >> Since it's a short refname, we first try to look it up as a tag: > >No, you don't do even that. > >The name is "fixes". But you seem to match it with one of these: > >> $ git ls-remote git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal fixes^{} >> a6d25f4c951b8b28f2eaec6f891ff834622532f2 refs/tags/omap-for-v3.10-rc1/fixes^{} >> 77319669af37a1cfc844b801e83343b37e3c7e13 refs/tags/omap/fixes^{} > >*NEITHER* of which is a tag named "fixes". One is named >"omap-for-v3.10-rc1/fixes" and the other is a tag named "omap/fixes". Linus: Thank you for the feedback. I've implemented a fix that handles shortname refs more properly in order to avoid hitting this problem again. Regards, -K