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 [thread overview]
Message-ID: <20180606142003.GS8514@sasha-vm> (raw)
In-Reply-To: <40C3380A-0BDD-43B3-B675-F263B169A0E3@prjkt.io>
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 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 :)
next prev parent reply other threads:[~2018-06-06 14:20 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 4:00 [GIT PULL] commits for Linux 3.18 Sasha Levin
2018-06-05 6:42 ` Harsh Shandilya
2018-06-05 7:30 ` Sasha Levin
2018-06-05 9:09 ` Harsh Shandilya
2018-06-05 18:46 ` Sasha Levin
2018-06-05 18:54 ` Harsh Shandilya
2018-06-05 18:59 ` Sasha Levin
2018-06-05 19:49 ` Harsh Shandilya
2018-06-06 14:20 ` Sasha Levin [this message]
2018-06-06 20:55 ` Harsh Shandilya
-- strict thread matches above, loose matches on Subject: below --
2018-11-12 3:26 Sasha Levin
2018-11-05 19:11 Sasha Levin
2018-10-22 9:14 Sasha Levin
2018-10-16 16:40 Sasha Levin
2018-10-12 14:36 Sasha Levin
2018-10-08 15:02 Sasha Levin
2018-10-02 0:58 Sasha Levin
2018-09-28 0:26 Sasha Levin
2018-09-24 1:01 Sasha Levin
2018-09-17 23:46 Sasha Levin
2018-09-14 18:41 Sasha Levin
2018-09-10 14:28 Sasha Levin
2018-08-25 15:10 Sasha Levin
2018-08-28 14:11 ` Greg KH
2018-08-10 0:23 Sasha Levin
2018-08-22 8:45 ` Greg KH
2018-07-28 1:46 Sasha Levin
2018-07-28 10:54 ` Greg KH
2018-06-21 2:38 Sasha Levin
2018-07-05 18:20 ` Greg KH
2018-06-07 1:07 Sasha Levin
2018-05-19 16:59 Sasha Levin
2018-05-19 19:18 ` Harsh Shandilya
2018-05-28 8:04 ` Greg KH
2018-05-28 8:18 ` Greg KH
2018-05-28 8:47 ` Harsh Shandilya
2018-05-28 9:02 ` Greg KH
2018-04-27 2:01 Sasha Levin
2018-05-02 20:49 ` Greg KH
2018-04-15 21:38 Sasha Levin
2018-04-24 17:05 ` Greg KH
2018-04-26 16:19 ` Sasha Levin
2018-04-26 18:40 ` Harsh Shandilya
2018-04-05 6:24 Sasha Levin
2018-04-05 7:02 ` Harsh Shandilya
2018-04-05 7:40 ` Nathan Chancellor
2018-04-09 0:26 ` Sasha Levin
2018-04-09 12:04 ` Greg KH
2018-04-09 15:12 ` Greg KH
2018-04-09 16:14 ` Nathan Chancellor
2018-04-09 17:41 ` Greg KH
2018-04-09 17:08 ` Harsh Shandilya
[not found] ` <43DEA09E-D11B-4563-929A-50612C9BF724@gmail.com>
2018-04-05 7:26 ` Harsh Shandilya
2018-04-10 13:15 ` Greg KH
2018-03-19 15:38 Sasha Levin
2018-03-22 14:17 ` Greg KH
2018-03-15 22:41 Sasha Levin
2018-03-19 13:37 ` Greg KH
2018-02-25 0:59 Sasha Levin
2018-02-28 15:17 ` Greg KH
2018-02-04 16:04 Sasha Levin
2018-02-23 11:02 ` Greg KH
2018-01-28 22:32 Sasha Levin
2017-12-20 15:37 alexander.levin
2017-12-22 8:41 ` Greg KH
2017-12-14 16:13 alexander.levin
2017-12-18 14:05 ` Greg KH
2017-12-12 0:59 alexander.levin
2017-12-14 20:38 ` Greg KH
2017-12-02 15:46 alexander.levin
2017-12-06 15:39 ` Greg KH
2017-12-06 16:23 ` alexander.levin
2017-12-06 16:31 ` Greg KH
2017-11-30 22:02 alexander.levin
2017-12-02 8:50 ` Greg KH
2017-12-02 15:46 ` alexander.levin
2017-11-30 22:02 alexander.levin
2017-12-02 8:50 ` Greg KH
2017-11-30 22:02 alexander.levin
2017-12-01 9:13 ` Greg KH
2017-12-01 15:26 ` alexander.levin
2017-12-02 8:51 ` Greg KH
2017-11-24 17:14 alexander.levin
2017-11-28 9:59 ` Greg KH
2017-11-19 0:51 alexander.levin
2017-11-19 11:17 ` Greg KH
2017-11-08 20:45 Levin, Alexander (Sasha Levin)
2017-11-09 17:23 ` Greg KH
2017-10-25 1:40 Levin, Alexander (Sasha Levin)
2017-11-06 11:25 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180606142003.GS8514@sasha-vm \
--to=alexander.levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=harsh@prjkt.io \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.