public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] arch/parisc fixes for 2.6.31-rc6
Date: Sun, 02 Aug 2009 20:46:18 +0200	[thread overview]
Message-ID: <4A75DEFA.1070009@gmx.de> (raw)
In-Reply-To: <20090802180636.GB28572@bombadil.infradead.org>

On 08/02/2009 08:06 PM, Kyle McMartin wrote:
> On Sun, Aug 02, 2009 at 07:51:29PM +0200, Helge Deller wrote:
>> On 08/02/2009 07:21 PM, Kyle McMartin wrote:
>>> On Sun, Aug 02, 2009 at 07:02:22PM +0200, Helge Deller wrote:
>>>> Hi Linus,
>>>>
>>>> please pull the following changes for the HP parisc architecture.
>>> Uhm, I didn't authorize you to do this...
>> I'm equally authorized like you.
>>
>> MAINTAINERS file shows:
>> PARISC ARCHITECTURE
>> M:      Kyle McMartin<kyle@mcmartin.ca>
>> M:      Helge Deller<deller@gmx.de>
>
> That's not how this works.

Cool. Great argument!

>>> WTF?
>> During the development cycle of 2.6.26 up to 2.6.30, many
>> patches were not pushed upstream by someone.
>> Now I'm having a whole lot of work to push the missing patches
>> back into the stable-kernel and debian kernel series.
>> That's the reason I don't want that those patches miss 2.6.31 too...
>>
>
> Then send *me* a pull request. Don't give me a bloody end-around, it's
> simply unacceptable behaviour.

I'm missing a very important thing here:
Can you guarantee, that you will push things upstream in time?
If yes, I'm fine with sending you a push request.
If not, I don't see any other way.

Helge

  reply	other threads:[~2009-08-02 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-02 17:02 [GIT PULL] arch/parisc fixes for 2.6.31-rc6 Helge Deller
2009-08-02 17:21 ` Kyle McMartin
2009-08-02 17:51   ` Helge Deller
2009-08-02 18:06     ` Kyle McMartin
2009-08-02 18:46       ` Helge Deller [this message]
2009-08-04  2:39 ` Kyle McMartin
2009-08-04 21:01   ` 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=4A75DEFA.1070009@gmx.de \
    --to=deller@gmx.de \
    --cc=kyle@mcmartin.ca \
    --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