[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181231143300.51310ce3@gandalf.local.home>
Date: Mon, 31 Dec 2018 14:33:00 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Tom Zanussi <tom.zanussi@...ux.intel.com>,
Namhyung Kim <namhyung@...nel.org>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Joe Perches <joe@...ches.com>,
Andreas Schwab <schwab@...ux-m68k.org>
Subject: Re: [GIT PULL] tracing: Update for 4.21
On Mon, 31 Dec 2018 10:17:41 -0800
Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> On Fri, Dec 28, 2018 at 3:28 PM Steven Rostedt <rostedt@...dmis.org> wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> > trace-v4.21
>
> No such tag.
>
Ug!
> > Tag SHA1: bcf1ea7cb12ce702d1d0660dfba0c3462c0b04e1
> > Head SHA1: 3d739c1f6156c70eb0548aa288dcfbac9e0bd162
>
> I can see branches with that commit SHA ("for-next" and "ftrace/core")
> but there is no tag with that name or that SHA1.
>
> Forgot to push out?
Yeah, I did. I just pushed it out.
>
> Btw, please don't include the whole diff in the same email when it's
> ~seven thousand lines and over 200k in size. Yeah, I'm on a fast
> connection, but that isn't *always* true. Did lkml even take this
> email?
OK, I'll modify my script not to make that diff.
It does appear to have still made it to LKML. I received it in my LKML
folder with:
X-Mailing-List: linux-kernel@...r.kernel.org
-- Steve
Powered by blists - more mailing lists