From: Samuel Jean <sj-netfilter@cookinglinux.org>
To: "Samuel Díaz García" <samueldg@arcoscom.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Suggestions for some patch-o-matic extensions (comment, ipp2p, random, etc...)
Date: Wed, 16 Feb 2005 18:15:15 -0500 [thread overview]
Message-ID: <4213D403.3000202@cookinglinux.org> (raw)
In-Reply-To: <4213CF7F.6060901@arcoscom.com>
Samuel Díaz García wrote:
> I don't know how to use diff/patch utils to send you a patch to solve
> these issues, if anybody say me how to use them to create a valid patch
> file and send to the list.
Hi Samuel,
Well, first off. Please post such subject on the
netfilter-devel@lists.netfilter.org
>
> I suppose that I need some rules over the file names and so on, say me
> and I post the patch.
If you are going to patch kernel part.. uhm. if you are going to patch
at all, please read Documentation/SubmittingPatches and CodingStyle.
(from linux kernel source)
>
> I have the patched files too, but I don't know if I can send attached
> files to the list.
Well, that should be the really _last_ thing you do. Prior to this,
you should :
1. Post the complete errors you got
2. Manage to make some patches
Oh! Here's a good reading :
http://www.csn.ul.ie/~mel/projects/vm/guide/html/understand/node13.html#SECTION00611000000000000000
> Samuel Díaz García
> Director Gerente
> ArcosCom Wireless, S.L.L.
Thanks a lot,
Samuel
next prev parent reply other threads:[~2005-02-16 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 22:19 Suggestions for some patch-o-matic extensions (comment, ipp2p, random, etc...) Samuel Díaz García
2005-02-16 22:55 ` Samuel Díaz García
2005-02-16 23:15 ` Samuel Jean [this message]
[not found] ` <4213DB25.1080604@arcoscom.com>
2005-02-17 0:00 ` Samuel Jean
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=4213D403.3000202@cookinglinux.org \
--to=sj-netfilter@cookinglinux.org \
--cc=netfilter@lists.netfilter.org \
--cc=samueldg@arcoscom.com \
--cc=sjean@cookinglinux.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.