All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Andrew Beverley <andy@andybev.com>
Cc: lartc@mailman.ds9a.nl, netfilter-devel@lists.netfilter.org,
	linux@arcoscom.com
Subject: Re: [LARTC] Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues]
Date: Wed, 31 Jan 2007 03:58:51 +0100	[thread overview]
Message-ID: <45C005EB.1040704@netfilter.org> (raw)
In-Reply-To: <1169746884.4253.51.camel@andybev.localdomain>

Andrew Beverley wrote:
> I would also like to see as many of the POM included in the stable
> kernel. It's a bit of a headache to patch in what I want each time I
> update the kernel, and on a fresh system I have to install CURL just to
> update POM just to add connlimit to the kernel...

IMHO, patching kernels to add some certain shiny-feature(TM) is
generally a bad idea if you don't know how the patch internally works or
if you can't directly get support from the author of such patch.
Moreover, if the applied patchset is large, this can become a problem
since, at some point, you could report unreproducible bugs probably
introduced by one of your patches, thus annoying developers that are
worried about fixing bugs in the stable kernel branch asap. So, I would
suggest people to be more conservative when applying patches.

Anyway, if you think that some certain patch is stable enough to push it
forward to mainline, encourage the author to push it forward. Probably
there is a reason why he decided not to do that.

-- 
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris

  reply	other threads:[~2007-01-31  2:58 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11 19:44 [LARTC] iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues ArcosCom Linux User
2006-12-11 19:44 ` ArcosCom Linux User
2006-12-12  8:24 ` [LARTC] " ArcosCom Linux User
2006-12-12  8:24   ` ArcosCom Linux User
2006-12-12  8:33   ` Lutz Jaenicke
2006-12-12  8:34   ` [LARTC] " Patrick McHardy
2006-12-12  8:34     ` Patrick McHardy
2006-12-13  8:31     ` [LARTC] " ArcosCom Linux User
2006-12-13  8:31       ` ArcosCom Linux User
2006-12-13  8:38       ` [LARTC] " Patrick McHardy
2006-12-13  8:38         ` Patrick McHardy
2006-12-13  9:12         ` [LARTC] " ArcosCom Linux User
2006-12-13  9:12           ` ArcosCom Linux User
2006-12-13  9:17           ` [LARTC] " Patrick McHardy
2006-12-13  9:17             ` Patrick McHardy
2006-12-13 11:00             ` Jan Engelhardt
2006-12-13 10:56         ` Jan Engelhardt
2006-12-28 21:10         ` Krzysztof Oledzki
2007-01-10  5:58           ` [LARTC] " Patrick McHardy
2007-01-10  5:58             ` Patrick McHardy
2007-01-10 11:53             ` Jan Engelhardt
2007-01-10 12:53               ` [LARTC] " Patrick McHardy
2007-01-10 12:53                 ` Patrick McHardy
2007-01-10 13:15               ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, ArcosCom Linux User
2007-01-10 13:15                 ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] ArcosCom Linux User
2007-01-10 14:08                 ` Jan Engelhardt
2007-01-10 13:21               ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, ArcosCom Linux User
2007-01-10 13:21                 ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] ArcosCom Linux User
2007-01-25 17:41                 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, Andrew Beverley
2007-01-25 17:41                   ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Andrew Beverley
2007-01-31  2:58                   ` Pablo Neira Ayuso [this message]
2007-02-09 13:37                     ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, Andrew Beverley
2007-02-09 13:37                       ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Andrew Beverley
2007-02-09 16:57                       ` Krzysztof Oledzki
2007-02-09 17:03                         ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, kernel Patrick McHardy
2007-02-09 17:03                           ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Patrick McHardy
2007-02-09 17:30                         ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, Andrew Beverley
2007-02-09 17:30                           ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Andrew Beverley

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=45C005EB.1040704@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=andy@andybev.com \
    --cc=lartc@mailman.ds9a.nl \
    --cc=linux@arcoscom.com \
    --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.