lkml.org 
[lkml]   [2019]   [Feb]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [GIT PULL] Thermal-SoC management fixes for v5.0-rc6
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

\
 
 \ /
  Last update: 2019-02-12 00:11    [W:0.040 / U:4.428 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site