Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Arnt Karlsen <arnt@c2i.net>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: can't patch with patch-o-matic
Date: 18 Feb 2003 16:45:35 +0100	[thread overview]
Message-ID: <1045583134.18515.159.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <20030218153758.6e6d806a.arnt@c2i.net>

On Tue, 2003-02-18 at 15:37, Arnt Karlsen wrote:

> > Patch-o-matic is cool in that it handles a lot of this
> > stuff without problems, but if you are applying too many patches
> > on top of each other, you should resolve any conflicts yourself...
> 
> ..this attitude is not good enough.  As a minimum, all the base patches
> should make it into "my" patched kernel, starting from a _clean_ Linus
> tree.  The extras etc, should stop and warn that "this" patch does not
> "allow" etc "that" patch, "so, you need to choose which you want".  

This attitude is perfectly fine, if you don't like it, start running an
OS you can't modify. You find this attitude _everywhere_ in the Linux
community. If you want to be able to do more advanced stuff you will
have to actually learn how to do parts of it yourself.
I can tell you that patch-o-matic already does a lot of things to help
you apply all these patches. With regular patch files you would have to
fix a lot by hand.

Base patches go in without any problems here, it's some of the extra
stuff that's the problem.

If you want that kind of dependency system you will have to fix it
yourself, I don't think any of the developers are interested in building
it.

> ..preferably, patch-o-matic should also work as good with Red Hat
> kernels, up to and including "base", as Red Hat and its derivatives 
> are the entry level distros.  From "extra and up", work from the 
> vanilla kernel trees.  

This you would definately have to fix yourself. Do you have any idea
what vendor kernels include? They include several hundred patches.

> ..and, I'd like to have Patch-o-matic log what it does, to a file, 
> either as the default, or as a suggestion on how to do it from the 
> cli, in a readme, as you see, people come here to learn.

We live in a do it yourself world, you can't rely on other people
building the stuff you want. If you want to see it built you will
probably have to build it yourself.

If you modify patch-o-matic to do this stuff we will review the changes
and either accept (possibly after some modifications) or reject them.

-- 
/Martin

Never argue with an idiot. They drag you down to their level, then beat you with experience.


  reply	other threads:[~2003-02-18 15:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18 12:53 can't patch with patch-o-matic Sneppe Filip
2003-02-18 14:37 ` Arnt Karlsen
2003-02-18 15:45   ` Martin Josefsson [this message]
2003-02-18 20:01     ` Arnt Karlsen
2003-02-21  8:38       ` Fabrice MARIE
2003-02-18 15:37 ` Luis Miguel Cruz Miranda
2003-02-18 19:56   ` Jozsef Kadlecsik
  -- strict thread matches above, loose matches on Subject: below --
2003-02-17 16:27 Luis Miguel Cruz Miranda
2003-02-18  5:32 ` Raymond Leach
2003-02-18 12:32   ` Luis Miguel Cruz Miranda
2003-02-18 12:48     ` Jozsef Kadlecsik

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=1045583134.18515.159.camel@tux.rsn.bth.se \
    --to=gandalf@wlug.westbo.se \
    --cc=arnt@c2i.net \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox