public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, rostedt@goodmis.org
Subject: Re: [patch] ftrace, v15
Date: Sun, 27 Apr 2008 00:22:16 -0700 (PDT)	[thread overview]
Message-ID: <20080427.002216.165148751.davem@davemloft.net> (raw)
In-Reply-To: <20080427071659.GA13036@elte.hu>

From: Ingo Molnar <mingo@elte.hu>
Date: Sun, 27 Apr 2008 09:16:59 +0200

> * David Miller <davem@davemloft.net> wrote:
> 
> > You're getting sloppier and sloppier each and every bogus pull request 
> > you send out this week Ingo.
> 
> this is not a pull request David ...
> 
> > What is all of this non-ftrace crap in the shortlog?
> 
> other changes in my tree ...

Regardless of what it is, I'm getting really sick and tired of how
you're doing development during this merge window and all of the
completely bogus and unreviewed changes you are inserting into the
tree at a freightening pace.

Someone posting a patch to LkML and YOU applying the patch to your
tree DOES NOT equal "reviewed"!

If nobody has had a chance to review the patch, too bad.

By jamming all of this stuff into Linus's tree, you are forcing poor
souls like myself and Andrew Morton to watch over you like a small
child.  And that is totally unfair to those of us who have our own
merging and development work to do.

The code gets reviewed first, not after it's in the tree already.

Your little "let's see how fast I can merge patches into the tree"
experiment is coming at an enormous cost.

  reply	other threads:[~2008-04-27  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27  6:30 [patch] ftrace, v15 Ingo Molnar
2008-04-27  6:32 ` David Miller
2008-04-27  7:16   ` Ingo Molnar
2008-04-27  7:22     ` David Miller [this message]
2008-04-27 11:14 ` KOSAKI Motohiro
2008-04-27 13:15   ` Ingo Molnar

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=20080427.002216.165148751.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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