From: Linus Torvalds <torvalds@linux-foundation.org>
To: Matt Turner <mattst88@gmail.com>
Cc: Sinan Kaya <okaya@codeaurora.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Michael Cree <mcree@orcon.net.nz>,
linux-alpha@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PULL] alpha.git
Date: Mon, 9 Apr 2018 09:13:53 -0700 [thread overview]
Message-ID: <CA+55aFxthoBs7HiPBPDrJy-uw8MM+bM-=CZYz4Tdtn8GALUNdQ@mail.gmail.com> (raw)
In-Reply-To: <20180408184409.GA27396@ivybridge.mattst88.com>
On Sun, Apr 8, 2018 at 11:44 AM, Matt Turner <mattst88@gmail.com> wrote:
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mattst88/alpha.git
> for you to fetch changes up to cd0e00c106722eca40b38ebf11cf134c01901086:
They aren't actually where you claimed.
They are in the completely unmentioned "for-linus" branch.
Yes, yes, I can figure that out on my own (particularly since you gave
me the commit for the branch head, so I can verify using "git
ls-remote" even before pulling), but I really would like to see it in
the pull request.
Linus
next prev parent reply other threads:[~2018-04-09 16:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 18:44 [PULL] alpha.git Matt Turner
2018-04-09 16:13 ` Linus Torvalds [this message]
2018-04-09 16:46 ` Matt Turner
-- strict thread matches above, loose matches on Subject: below --
2023-02-25 20:40 Matt Turner
2023-02-25 20:51 ` Linus Torvalds
2023-02-25 21:10 ` pr-tracker-bot
2021-07-30 3:08 Matt Turner
2021-07-30 5:13 ` pr-tracker-bot
2020-06-13 0:57 Matt Turner
2020-06-13 18:00 ` pr-tracker-bot
2019-02-11 4:46 Matt Turner
2019-02-11 18:35 ` pr-tracker-bot
2018-12-30 22:25 Matt Turner
2018-12-31 18:05 ` pr-tracker-bot
2018-05-23 4:02 Matt Turner
2018-02-02 19:52 Matt Turner
2018-01-21 2:25 Matt Turner
2018-01-23 10:23 ` Mikulas Patocka
2018-01-23 17:56 ` Matt Turner
2018-01-24 9:55 ` Mikulas Patocka
2017-09-04 20:50 Matt Turner
2017-08-29 19:35 Matt Turner
2012-05-24 18:43 Matt Turner
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='CA+55aFxthoBs7HiPBPDrJy-uw8MM+bM-=CZYz4Tdtn8GALUNdQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=okaya@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).