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@xxxxxxxxxxxxx> 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 this 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 :)
