From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Mon, 28 May 2018 15:23:26 +0300 [thread overview]
Message-ID: <CAHp75VdV-rpqjkGxjAa_7q2rpkuGgy+6OScsP8BGCgRcbtgiaA@mail.gmail.com> (raw)
In-Reply-To: <20180525173025.GO4828@sirena.org.uk>
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.
P.S. It broke my scripts to automatically rebase my local working
branches, though it's not big deal per se, rather above is an issue.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2018-05-28 12:23 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 [this message]
2018-05-29 10:38 ` Mark Brown
2018-05-29 11:18 ` Stephen Rothwell
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=CAHp75VdV-rpqjkGxjAa_7q2rpkuGgy+6OScsP8BGCgRcbtgiaA@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=broonie@kernel.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).