From: "David S. Miller" <davem@redhat.com>
To: mk@linux-ipv6.org
Cc: jmorris@intercode.com.au, kuznet@ms2.inr.ac.ru,
netdev@oss.sgi.com, usagi@linux-ipv6.org
Subject: Re: [PATCH] IPV4 IPComp : threshold comparison
Date: Sat, 17 May 2003 22:34:23 -0700 (PDT) [thread overview]
Message-ID: <20030517.223423.26296484.davem@redhat.com> (raw)
In-Reply-To: <87smrda4q6.wl@karaba.org>
From: Mitsuru KANDA / 神田 充 <mk@linux-ipv6.org>
Date: Sun, 18 May 2003 02:00:01 +0900
===== ipcomp.c 1.6 vs edited =====
--- 1.6/net/ipv4/ipcomp.c Tue May 13 05:58:03 2003
+++ edited/ipcomp.c Sun May 18 01:42:22 2003
I am applying this, but please you USAGI guys start to
generate properly rooted patched for me ok?
I want something of the form:
--- a/net/ipv4/ipcomp.c Tue May 13 05:58:03 2003
+++ b/net/ipv4/ipcomp.c Sun May 18 01:42:22 2003
Almost everyone sends me patches like this, USAGI are
the one exception. If everyone sends me patches this
way, then all of my patch applying scripts know they can
simply use "patch -p1" when sitting at top of kernel tree.
Probably all of the USAGI patches look this way because of
CVS or something like that.
Thank you.
prev parent reply other threads:[~2003-05-18 5:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 17:00 [PATCH] IPV4 IPComp : threshold comparison Mitsuru KANDA / 神田 充
2003-05-18 1:07 ` James Morris
2003-05-18 5:34 ` David S. Miller [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=20030517.223423.26296484.davem@redhat.com \
--to=davem@redhat.com \
--cc=jmorris@intercode.com.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mk@linux-ipv6.org \
--cc=netdev@oss.sgi.com \
--cc=usagi@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).