mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][GIT PULL][v3.3] ktest: Fix make_min_config test when build fails
Date: Mon, 27 Feb 2012 18:32:54 -0500	[thread overview]
Message-ID: <1330385574.25686.200.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <CA+55aFw5hhQQU-X_n=Q98Xt_UVKUgeVJ53BhwDgFvXSSt_0Bjw@mail.gmail.com>

On Mon, 2012-02-27 at 15:26 -0800, Linus Torvalds wrote:
> On Mon, Feb 27, 2012 at 11:17 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > Please pull the latest for-linus tree, which can be found at:
> >
> >  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
> > ktest-fix-make-min-failed-build
> 
> I'm getting "Already up-to-date" with that tag. It points to your old
> commit be405f95f0a0 ("ktest: Add INGORE_ERRORS to ignore warnings in
> boot up") and normally I'd ask whether you perhaps forgot to push, but
> considering the fairly unique naming of that tag, you clearly *did*
> push.

Crap! I haven't gotten the scripts working yet with the signed tags. It
tagged then merged the latest commit :-p

> 
> Congratulations, you seem to have found a whole new and unique way of
> screwing up ;)

I knew I was good at something!

I'll go fix.

Thanks,

-- Steve

> 
>                Linus "my mom called me 'special' too" Torvalds



  reply	other threads:[~2012-02-27 23:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 19:17 Steven Rostedt
2012-02-27 23:26 ` Linus Torvalds
2012-02-27 23:32   ` Steven Rostedt [this message]
2012-02-27 23:36     ` Linus Torvalds
2012-02-27 23:49       ` Steven Rostedt
2012-02-27 23:38   ` Steven Rostedt
2012-02-27 23:44     ` Linus Torvalds

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=1330385574.25686.200.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®