From: Patrick McHardy <kaber@trash.net>
To: Johannes Graumann <graumann@caltech.edu>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: patch-o-matic-ng questions and remarks from newbie
Date: Mon, 15 Nov 2004 23:23:10 +0100 [thread overview]
Message-ID: <41992C4E.2050809@trash.net> (raw)
In-Reply-To: <20041115141326.4ced89bc@localhost>
Johannes Graumann wrote:
>Thanks,
>
>I found those and have finally managed to get my kernel to compile.
>One general question of mine remains unsolved: is there - aside from
>trial and error - some way to figure out which patch in the
>patch-o-matic-ng plays well with what kernel?
>
They should have dependencies that are automatically checked,
but usually something like "kernel >= 2.6.7 is used", this of
course doesn't catch future versions that the patch won't work
with anymore.
Regards
Patrick
next prev parent reply other threads:[~2004-11-15 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 18:28 patch-o-matic-ng questions and remarks from newbie Johannes Graumann
2004-11-07 21:08 ` Patrick McHardy
2004-11-15 22:13 ` Johannes Graumann
2004-11-15 22:23 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-05 4:20 Johannes Graumann
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=41992C4E.2050809@trash.net \
--to=kaber@trash.net \
--cc=graumann@caltech.edu \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.