All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Poulin" <jeromepoulin@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: 3896 pom-ng broken
Date: Tue, 10 May 2005 15:15:25 -0400	[thread overview]
Message-ID: <debc30fc050510121564dd0703@mail.gmail.com> (raw)
In-Reply-To: <debc30fc0505101214699d85b8@mail.gmail.com>

On 5/10/05, Jérôme Poulin <jeromepoulin@gmail.com> wrote:
> See my e-mail, posted the same problem / solution and got no answer,
> only 3 patchs apply with that new snapshot, other patch with no
> requirements or even with a valid requirement won't apply, only set,
> h323, goto and another apply, anyway see my other mails.
> 
> On 5/10/05, Amin Azez <azez@ufomechanic.net> wrote:
> > Phil Oester wrote:
> >
> > >On Tue, May 10, 2005 at 12:15:19PM +0100, Amin Azez wrote:
> > >
> > >
> > >>This change
> > >>
> > >>http://svn.netfilter.org/cgi-bin/viewcvs.cgi/trunk/patch-o-matic-ng/Netfilter_POM.pm?rev=3896&r1=3820&r2=3896
> > >>
> > >>breaks pom-ng for me, such that it fails to apply most of the pom
> > >>patches because 2.6.11 seems to be the wrong source version.
> > >>
> > >>
> > >Perhaps this was intentional...which specific patches don't work, and did you verify
> > >the 'Requires' statement in the info file fits your kernel?
> > >
> > >
> > conntrack-event-api/info
> > Title: conntrack event API
> > Author: Pablo Neira <pablo@eurodev.net>
> > Status: Testing
> > Repository: extra
> > Requires: linux >= 2.6.11
> >
> > I was patching 2.6.11.7
> >
> > Amin
> >
> >
>

  parent reply	other threads:[~2005-05-10 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10 11:15 3896 pom-ng broken Amin Azez
2005-05-10 15:43 ` Phil Oester
2005-05-10 16:05   ` Amin Azez
     [not found]     ` <debc30fc0505101214699d85b8@mail.gmail.com>
2005-05-10 19:15       ` Jérôme Poulin [this message]
2005-05-11  0:51         ` Phil Oester
2005-05-17 15:05           ` Patrick McHardy

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=debc30fc050510121564dd0703@mail.gmail.com \
    --to=jeromepoulin@gmail.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.