From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 12
Date: Mon, 12 Aug 2019 15:38:06 +0200 [thread overview]
Message-ID: <CAMuHMdUEoBj-JBZza4==9TENfFk3BckCPO+mrZjhu1vOr05_0w@mail.gmail.com> (raw)
In-Reply-To: <20190812193146.4939f5f5@canb.auug.org.au>
Hi Stephen,
On Mon, Aug 12, 2019 at 11:33 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
Looks like commit 8e72ac275c63a44c ("Add linux-next specific files for
20190812")
made it to git.kernel.org, but the tag didn't?
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2019-08-12 13:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 9:31 linux-next: Tree for Aug 12 Stephen Rothwell
2019-08-12 13:38 ` Geert Uytterhoeven [this message]
2019-08-12 21:39 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2022-08-12 2:15 Stephen Rothwell
2022-08-12 7:08 ` Conor.Dooley
2021-08-12 8:39 Stephen Rothwell
2021-08-13 0:02 ` John Hubbard
2020-08-12 4:22 Stephen Rothwell
2016-08-12 4:03 Stephen Rothwell
2015-08-12 13:39 Stephen Rothwell
2014-08-12 4:52 Stephen Rothwell
2013-08-12 7:05 Stephen Rothwell
2011-08-12 7:13 Stephen Rothwell
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='CAMuHMdUEoBj-JBZza4==9TENfFk3BckCPO+mrZjhu1vOr05_0w@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).