From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 24
Date: Tue, 29 May 2018 21:18:59 +1000 [thread overview]
Message-ID: <20180529211859.583d7a48@canb.auug.org.au> (raw)
In-Reply-To: <20180529103850.GA23509@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
Hi Mark,
On Tue, 29 May 2018 11:38:50 +0100 Mark Brown <broonie@kernel.org> wrote:
>
> On Mon, May 28, 2018 at 03:23:26PM +0300, Andy Shevchenko wrote:
> > On Fri, May 25, 2018 at 8:30 PM, Mark Brown <broonie@kernel.org> wrote:
>
> > > Stephen should be back on Monday.
>
> > Your version has no tag which is crucial detail for easily getting
> > info what the current version is.
>
> That's generated by the scripts. They didn't complain about anything so
> I'm assuming it's somewhere in the kernel.org system and will appear at
> some point.
I have now created a tag for next-20180525. It is an annotated tag but
not signed. It may be that my scripts error checking is not up to
scratch, sorry. :-(
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-05-29 11:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 17:30 linux-next: Tree for May 24 Mark Brown
2018-05-27 18:46 ` Mark Brown
2018-05-27 19:20 ` Stephen Rothwell
2018-05-28 9:08 ` Arnd Bergmann
2018-05-28 11:04 ` Mark Brown
2018-05-28 12:23 ` Andy Shevchenko
2018-05-29 10:38 ` Mark Brown
2018-05-29 11:18 ` Stephen Rothwell [this message]
2018-05-29 11:37 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2023-05-24 5:48 Stephen Rothwell
2022-05-24 9:26 Stephen Rothwell
2021-05-24 6:08 Stephen Rothwell
2019-05-24 4:07 Stephen Rothwell
2017-05-24 3:23 Stephen Rothwell
2016-05-24 2:43 Stephen Rothwell
2012-05-24 6:49 Stephen Rothwell
2011-05-24 4:02 Stephen Rothwell
2010-05-24 3:57 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=20180529211859.583d7a48@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.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).