Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Venkatesh. K" <venkatesh@cbayscribe.com>
To: "Netfilter@Lists.Netfilter.Org" <netfilter@lists.netfilter.org>
Subject: Re: Generate a unified patch for source RPM
Date: Sat, 4 Oct 2003 06:01:47 +0530	[thread overview]
Message-ID: <01b601c38a0e$eb0d79d0$2800a8c0@karu> (raw)
In-Reply-To: 20031003105021.GE5758@sunbeam.de.gnumonks.org

Thanks a lot.

I had tried the same command line except the full path to the patch :(

Venkatesh K

----- Original Message ----- 
From: "Harald Welte" <laforge@netfilter.org>
To: "Venkatesh. K" <venkatesh@cbayscribe.com>
Cc: <>
Sent: Friday, October 03, 2003 4:20 PM
Subject: Re: Generate a unified patch for source RPM

On Thu, Sep 25, 2003 at 09:42:48PM +0530, Venkatesh. K wrote:
> Hi,
>
> I want to patch the RedHat Kernel RPM.
>
> How do I generate a single patch file from patch-o-matic which can be
> applied to an src.rpm ?

# pom2patch - create a normal unified diff (patch) from patch-o-matic

included in the patch-o-matic directory

syntax is:

pom2patch my_kernel_source_dir submitted/00_foo.patch

(you have to run it seperately for every patch-o-matic patch)

> Venkatesh K
-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie



      reply	other threads:[~2003-10-04  0:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25 16:12 Generate a unified patch for source RPM Venkatesh. K
2003-10-03 10:50 ` Harald Welte
2003-10-04  0:31   ` Venkatesh. K [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='01b601c38a0e$eb0d79d0$2800a8c0@karu' \
    --to=venkatesh@cbayscribe.com \
    --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