From: Fabrice MARIE <fabrice@netfilter.org>
To: Arnt Karlsen <arnt@c2i.net>, netfilter@lists.netfilter.org
Subject: Re: can't patch with patch-o-matic
Date: Fri, 21 Feb 2003 16:38:42 +0800 [thread overview]
Message-ID: <200302211638.43076.fabrice@netfilter.org> (raw)
In-Reply-To: <20030218210113.21d55422.arnt@c2i.net>
Hello,
On Wednesday 19 February 2003 04:01, Arnt Karlsen wrote:
> > [...]
> ..we disagree. Now, note I said "my" etc. This attitude has the
> wee problem it makes patch testing a little harder for the newbies,
> because the newbies never learns how they can report back new
> failures, which the attitude guys hasn't been been smart enough to
> prevent. This again has ramifications on development. Your call.
Don't get us wrong, but I thought we wrote already _a lot_ of documentation
that help people go through the installation of patches from patch-o-matic.
For instance, you have a README files distributed with patch-o-matic,
you have the excelent iptables tutorial written by Oskar Andreasson and contributors,
you have the netfilter-extensions-HOWTO on netfilter web site in the documentation
part, there are probably other documents, and of course, you have the source code ! :)
We don't mean to discourage newbies at all. hey, everybody started a newbie. I just
wish sometimes they would try harder before complaining. As Martin explained, patch-o-matic
makes it as easy as it can get to apply patches. We can hardly do better.
Finally (but please don't be discouraged nor offensed, that the way to learn), tcp-window-tracking
is not really for newbies as half of the patches in extra/,
you most probably don't need that if you just toy around. Instead, I recommend you to
work with patches in base/ as they are easier to deal with.
> > [...]
> > 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.
> ..agreed. Meanwhile, the Patch-o-matic readme might be made more
> useful for newbies after including a pointer to these wee '2>&1 >'
> tricks in, say, the abs-guide, unless it hurts someone attitude
> toe or something. Newbies who use patch-o-matic are smart enough
> to read and be made useful testing stuff for development.
As I said earlier, I believe there's plenty of docs on p-o-m out there.
But of course, if any of them if not complete enough, patches to the
documentation are welcome :)
Have a nice day,
Fabrice.
--
Fabrice MARIE
"Silly hacker, root is for administrators"
-Unknown
next prev parent reply other threads:[~2003-02-21 8:38 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
2003-02-18 20:01 ` Arnt Karlsen
2003-02-21 8:38 ` Fabrice MARIE [this message]
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=200302211638.43076.fabrice@netfilter.org \
--to=fabrice@netfilter.org \
--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 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.