From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
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 Dec 6
Date: Fri, 6 Dec 2019 23:43:00 +1100 [thread overview]
Message-ID: <20191206234300.5071290a@canb.auug.org.au> (raw)
In-Reply-To: <CAMuHMdVHXYhXtyMAR84L5kQTSU8Ds71AJftrEBqepiy_NV88kA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
Hi Geert,
On Fri, 6 Dec 2019 11:15:49 +0100 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> On Fri, Dec 6, 2019 at 3:55 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Changes since 20191204:
>
> Hm, yesterday there was a next-20191205.
Yeah, the script that updates this depends on today's tag being created
...
> Looks like the next-20191206 tag didn't make it to kernel.org, but the
> master branch was updated (so I'm happy :-)
... and there was an error when the tag was supposed to be created that
I failed to notice :-(
I have added the tag and pushed it. Thanks for noticing and letting me know.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-12-06 12:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 2:54 linux-next: Tree for Dec 6 Stephen Rothwell
2019-12-06 10:15 ` Geert Uytterhoeven
2019-12-06 12:43 ` Stephen Rothwell [this message]
2019-12-06 16:17 ` linux-next: Tree for Dec 6 (objtool, lots in btrfs) Randy Dunlap
2019-12-11 13:49 ` David Sterba
2019-12-11 16:21 ` Randy Dunlap
2019-12-12 18:47 ` Josh Poimboeuf
2019-12-12 20:25 ` Randy Dunlap
2019-12-13 23:03 ` Randy Dunlap
2019-12-13 23:50 ` Josh Poimboeuf
2019-12-14 0:04 ` Randy Dunlap
2019-12-14 5:45 ` Josh Poimboeuf
2019-12-14 7:05 ` Randy Dunlap
2019-12-17 15:25 ` David Sterba
2020-01-17 17:26 ` Josh Poimboeuf
2020-01-17 20:28 ` Marco Elver
2020-01-17 21:26 ` Josh Poimboeuf
2020-01-17 22:22 ` Josh Poimboeuf
2019-12-17 15:29 ` David Sterba
2020-01-10 19:46 ` David Sterba
2020-01-17 15:28 ` Josh Poimboeuf
2020-01-17 16:50 ` David Sterba
2020-01-17 17:03 ` Josh Poimboeuf
2020-01-20 15:52 ` Josh Poimboeuf
-- strict thread matches above, loose matches on Subject: below --
2023-12-06 4:29 linux-next: Tree for Dec 6 Stephen Rothwell
2022-12-06 3:36 Stephen Rothwell
2021-12-06 8:46 Stephen Rothwell
2018-12-06 8:18 Stephen Rothwell
2018-12-06 9:32 ` Stephen Rothwell
2017-12-06 4:19 Stephen Rothwell
2016-12-06 4:21 Stephen Rothwell
2013-12-06 3:49 Stephen Rothwell
2012-12-06 6:48 Stephen Rothwell
2011-12-06 4:44 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=20191206234300.5071290a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 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).