From: Helge Deller <deller@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kyle@mcmartin.ca, linux-kernel@vger.kernel.org,
linux-parisc@vger.kernel.org
Subject: Re: [git patches] parisc for 2.6.32
Date: Tue, 06 Oct 2009 22:53:29 +0200 [thread overview]
Message-ID: <4ACBAE49.9020903@gmx.de> (raw)
In-Reply-To: <alpine.LFD.2.01.0910061035050.3432@localhost.localdomain>
Hi Linus,
On 10/06/2009 07:40 PM, Linus Torvalds wrote:
> 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, sadly it was not in time.
And of course it's no excuse, that you didn't received a real pull-request,
even after Kyle asked for feedback for his tree with his mail on LKML and
parisc-list on 2009-09-28:
http://www.pubbs.net/kernel/200909/123965/
> 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").
This patch really only touches parisc-specific files and it includes
important fixes without which the parisc kernel won't even compile and link.
So, it would help us parisc-porters a lot if you could do an exception and
still pull from Kyle's tree, even after this merge window has been closed.
At least, it would make me personally very happy...
Helge
prev parent reply other threads:[~2009-10-06 20:53 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
2009-10-06 17:52 ` Kyle McMartin
2009-10-06 20:53 ` Helge Deller [this message]
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=4ACBAE49.9020903@gmx.de \
--to=deller@gmx.de \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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;
as well as URLs for NNTP newsgroup(s).