From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail-co1nam03on0095.outbound.protection.outlook.com ([104.47.40.95]:52688
        "EHLO NAM03-CO1-obe.outbound.protection.outlook.com"
        rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
        id S1751533AbeFFOUH (ORCPT <rfc822;stable@vger.kernel.org>);
        Wed, 6 Jun 2018 10:20:07 -0400
From: Sasha Levin <Alexander.Levin@microsoft.com>
To: Harsh Shandilya <harsh@prjkt.io>
CC: Greg KH <gregkh@linuxfoundation.org>,
        "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [GIT PULL] commits for Linux 3.18
Date: Wed, 6 Jun 2018 14:20:04 +0000
Message-ID: <20180606142003.GS8514@sasha-vm>
References: <MW2PR2101MB092242F1C026D889F5F02279FB660@MW2PR2101MB0922.namprd21.prod.outlook.com>
 <4B43B1A8-318F-41FA-B3F9-124FA59F8DA5@prjkt.io>
 <20180605073051.GP8514@sasha-vm>
 <6D16B430-9129-416C-BC62-041024A8615F@prjkt.io>
 <20180605175818.GQ8514@sasha-vm>
 <B1D6BCDE-FD75-4FF1-9D17-DD3886ACD21D@prjkt.io>
 <20180605185953.GR8514@sasha-vm>
 <40C3380A-0BDD-43B3-B675-F263B169A0E3@prjkt.io>
In-Reply-To: <40C3380A-0BDD-43B3-B675-F263B169A0E3@prjkt.io>
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4FD766903E59BF42B4EB6D92AC1098C4@namprd21.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Wed, Jun 06, 2018 at 01:19:50AM +0530, Harsh Shandilya wrote:
>On 6 June 2018 12:29:58 AM IST, Sasha Levin <Alexander.Levin@microsoft.com=
> wrote:
>>>>From git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable
>>* [new tag]                   for-greg-3.18-02122017 ->
>>for-greg-3.18-02122017
>>* [new tag]                   for-greg-3.18-04022018 ->
>>for-greg-3.18-04022018
>>* [new tag]                   for-greg-3.18-04052018 ->
>>for-greg-3.18-04052018
>>* [new tag]                   for-greg-3.18-05062018 ->
>>for-greg-3.18-05062018
>>* [new tag]                   for-greg-3.18-11122017 ->
>>for-greg-3.18-11122017
>>* [new tag]                   for-greg-3.18-14122017 ->
>>for-greg-3.18-14122017
>>* [new tag]                   for-greg-3.18-15042018 ->
>>for-greg-3.18-15042018
>>* [new tag]                   for-greg-3.18-20122017 ->
>>for-greg-3.18-20122017
>>* [new tag]                   for-greg-3.18-23022018 ->
>>for-greg-3.18-23022018
>>* [new tag]                   for-greg-3.18-26042018 ->
>>for-greg-3.18-26042018
>>* [new tag]                   for-greg-3.18-28012018 ->
>>for-greg-3.18-28012018
>>* [new tag]                   for-greg-4.14-02122017 ->
>>for-greg-4.14-02122017
>>* [new tag]                   for-greg-4.14-04022018 ->
>>for-greg-4.14-04022018
>>* [new tag]                   for-greg-4.14-04052018 ->
>>for-greg-4.14-04052018
>>t [tag update]                for-greg-4.14-04062018 ->
>>for-greg-4.14-04062018
>> [...]
>>
>>So I *thought* that git fetch was working right, but really it wasn't
>>the case.
>
>It _was_ working fine, but the design is too weird to risk things like thi=
s by not being explicit with your options.

So the tags that get pulled depend on whether you have the corresponding
branch (object) locally? WTF

Anyways, could you please test out for-greg-3.18-05062018 before I send
it out? Now with less build bugs :)=