public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
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 Aug 12
Date: Tue, 13 Aug 2019 07:39:14 +1000	[thread overview]
Message-ID: <20190813073914.2465e92e@canb.auug.org.au> (raw)
In-Reply-To: <CAMuHMdUEoBj-JBZza4==9TENfFk3BckCPO+mrZjhu1vOr05_0w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 451 bytes --]

Hi Geert,

On Mon, 12 Aug 2019 15:38:06 +0200 Geert Uytterhoeven <geert@linux-m68k•org> wrote:
>
> Looks like commit 8e72ac275c63a44c ("Add linux-next specific files for
> 20190812")
> made it to git.kernel.org, but the tag didn't?

Thanks for letting me know.  I made some changes to my scripts for
yesterday and there was a bug that I did not notice :-(  I have added
the tag and pushed it our just now.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-08-12 21:39 UTC|newest]

Thread overview: 15+ 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
2019-08-12 21:39   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-12  4:27 Stephen Rothwell
2024-08-12  4:13 Stephen Rothwell
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=20190813073914.2465e92e@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=geert@linux-m68k$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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