From: David Miller <davem@davemloft.net>
To: hswong3i@gmail.com
Cc: netdev@vger.kernel.org, shemminger@osdl.org
Subject: Re: [PATCH] tcp-lp: prevent chance for oops
Date: Fri, 29 Sep 2006 14:19:40 -0700 (PDT) [thread overview]
Message-ID: <20060929.141940.39158284.davem@davemloft.net> (raw)
In-Reply-To: <3feffd230609291226n673d9aa4s2f16fbacd34cfc48@mail.gmail.com>
From: "Wong Edison" <hswong3i@gmail.com>
Date: Sat, 30 Sep 2006 03:27:00 +0800
> I do this since i have a sourceforge homepage for it. I update the
> CVS version there, test, and then submit to netdev. As I sync code
> in both side, this $Id$ is keeped. May you just let it be? I think
> it will let my maintenance become more simple...
You could not even generate a clean patch to me, it just
gets in the way and causes more work for me and anyone
else who tries to use your patches.
If you want to use versioning, use MODULE_VERSION() just like
everyone else in the kernel does.
next prev parent reply other threads:[~2006-09-29 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 10:43 [PATCH] tcp-lp: prevent chance for oops Wong Edison
2006-09-28 21:38 ` David Miller
2006-09-28 21:40 ` David Miller
2006-09-29 19:27 ` Wong Edison
2006-09-29 21:19 ` David Miller [this message]
2006-09-30 10:54 ` Wong Edison
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=20060929.141940.39158284.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hswong3i@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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