public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: kyle@mcmartin.ca
Cc: linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [git patches] parisc for 2.6.32
Date: Tue, 6 Oct 2009 10:40:10 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.01.0910061035050.3432@localhost.localdomain> (raw)
In-Reply-To: <20091006172602.GA1924@hera.kernel.org>



On Tue, 6 Oct 2009, Kyle McMartin wrote:
<
> Mostly fixes, except for the tracehook stuff...

I don't see how this can be fixes, since I can't recall any parisc pulls 
during the merge window.

Yes, there have been parisc changes, but they've all come in through 
commits that either were global and people also fixed up parisc while at 
it (eg things like "fcntl: add F_[SG]ETOWN_EX"), or they have been build 
cleanups where you were cc'd but apparently never even bothered to ack the 
change.

So now you come in after the merge window has been closed for over a week, 
and want to do a parisc merge?

Tell me why I should take this. Tell me why I shouldn't just wait until 
the next merge window (or rather "_you_ should have waited").

I've now had two pull requests just today that made me go "I don't really 
see why I should pull this after -rc3 is out".

			Linus

  reply	other threads:[~2009-10-06 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 17:26 [git patches] parisc for 2.6.32 Kyle McMartin
2009-10-06 17:40 ` Linus Torvalds [this message]
2009-10-06 17:52   ` Kyle McMartin
2009-10-06 20:53   ` Helge Deller

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=alpine.LFD.2.01.0910061035050.3432@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.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