public inbox for gentoo-kernel@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Volkov <pva@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: Re: [gentoo-kernel] Kernel patching solution.
Date: Fri, 28 Dec 2007 09:51:48 +0300	[thread overview]
Message-ID: <1198824708.6351.34.camel@localhost> (raw)
In-Reply-To: <47741389.1040409@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]


В Чтв, 27/12/2007 в 21:05 +0000, Daniel Drake пишет:
> As for other options: You could just install the patch to the filesystem 
> and require the user to apply it. Other packages do/did this, e.g. hdaps

Ok. Let's me suggest another way. I'd like to standardize (eclass) the
place such ebuilds install patches. Together with place, I'd like to add
information (may be in patch name or inside patch itself) what kernels
this patch supports. Is this the way to go?

After this I'm sure there will be no problem to have external tool to
simplify patching. If you do not like it - do not use it.

> But the only real solution is this: get the patch merged upstream, or 
> equivalent functionality offered in the mainline kernel. Everything else 
> is working against the flow of the kernel.

Eh. I see your intentions. But IMQ will never get upstream while me and
many other people are using it and AFAIK currently there is not
substitution for it (IFB is different). patch-o-matic patches are really
slow in moving to official tree, while I have to use it's functionality.
There will be always such patches.

-- 
Peter.

[-- Attachment #2: Эта часть сообщения подписана цифровой подписью --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2007-12-28  6:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-27 20:39 [gentoo-kernel] Kernel patching solution Peter Volkov
2007-12-27 21:05 ` Daniel Drake
2007-12-28  6:51   ` Peter Volkov [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=1198824708.6351.34.camel@localhost \
    --to=pva@gentoo.org \
    --cc=gentoo-kernel@lists.gentoo.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