From: Christoph Hellwig <hch@infradead.org>
To: Takashi Ikebe <ikebe.takashi@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH i386] Live Patching Function on 2.6.11.7
Date: Mon, 18 Apr 2005 06:21:35 +0100 [thread overview]
Message-ID: <20050418052135.GA16630@infradead.org> (raw)
In-Reply-To: <4263277F.6020206@lab.ntt.co.jp>
On Mon, Apr 18, 2005 at 12:20:31PM +0900, Takashi Ikebe wrote:
> The patch was over 50k, so I separate it to each architecture and in line..
>
> This patch add function called "Live patching" which is defined on
> OSDL's carrier grade linux requiremnt definition to linux 2.6.11.7 kernel.
Traditionally beeing in OSDL specs was a very good reason not to merge patches.
Can you please come up with real arguments instead of this requirements
bullshit. Also I hope OSDL would invest their money in more useful things
than CGL, why has this idiocy still not stopped?
prev parent reply other threads:[~2005-04-18 5:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 3:20 [PATCH i386] Live Patching Function on 2.6.11.7 Takashi Ikebe
2005-04-18 5:21 ` Christoph Hellwig [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=20050418052135.GA16630@infradead.org \
--to=hch@infradead.org \
--cc=ikebe.takashi@lab.ntt.co.jp \
--cc=linux-kernel@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