From: Fabrice MARIE <fabrice@celestix.com>
To: Patrick McHardy <kaber@trash.net>, netfilter-devel@lists.samba.org
Subject: Re: MARK_operations
Date: Fri, 7 Jun 2002 11:59:41 +0800 [thread overview]
Message-ID: <200206071159.41320.fabrice@celestix.com> (raw)
In-Reply-To: <3CFF8D02.9000003@trash.net>
Hello Patrick,
On Friday 07 June 2002 00:25, Patrick McHardy wrote:
> Hi.
> Why was the MARK_operations patch moved to broken in latest CVS version ?
MARK_operations was not moved there as far as I can remeber, it was checked'in there
from the begining, because people experienced problem applying the patch. This was
due to a bug I introduced in the ./runme script (fixed for some time now),
and not due to the patch itself. So far, the patch has been working for me.
I simply move it to extra/ before applying patches from p-o-m.
When the coreteam has a bit of time, they'll probably move it there.
Have a nice day,
Fabrice.
--
Fabrice MARIE
Senior R&D Engineer
Celestix Networks
http://www.celestix.com/
"Silly hacker, root is for administrators"
-Unknown
prev parent reply other threads:[~2002-06-07 3:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 16:25 MARK_operations Patrick McHardy
2002-06-07 3:59 ` Fabrice MARIE [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=200206071159.41320.fabrice@celestix.com \
--to=fabrice@celestix.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.samba.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.