public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: James Morris <jmorris@namei.org>
Cc: David Miller <davem@davemloft.net>,
	alan@lxorguk.ukuu.org.uk, kuznet@ms2.inr.ac.ru,
	pekkas@netcore.fi, yoshfuji@linux-ipv6.org, kaber@coreworks.de,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2.6.17-rc6-mm1 ] net: RFC 3828-compliant UDP-Lite support
Date: Thu, 8 Jun 2006 21:09:33 +0100	[thread overview]
Message-ID: <200606082109.34338.gerrit@erg.abdn.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0606081542390.3555@d.namei>

Quoting James Morris:
|  On Thu, 8 Jun 2006, David Miller wrote:
|  
|  > > Understood. Please, anyone, disregard or un-apply the previous
|  > > UDP-Lite patch.  A revised patch will be prepared and posted as soon
|  > > as testing permits.
|  > 
|  > Nobody is going to integrate your patch anywhere, don't worry.
|  > You make it clear that once you toss this piece of code over
|  > the wall, you'll disappear.
|  
|  Having dealt with more than enough code thrown over the wall in recent 
|  times, I agree.

I understand the points of both of you well enough. But how come this is interpreted 
as saying I'd "toss this piece of code over the wall"? I can understand getting tired 
of cowboy coding jobs, but there is a misunderstanding here.

Of course do and will I maintain that code and every issue related it. I have been
maintaining, improving, testing this code for 9 months. The protocol spec (RFC 3828)
was developed at University of Aberdeen, and there is continuing research into 
UDP-Lite here, i.e. it is not a `dead' project. That is why I held back regarding the 
IPv6 port: I can ensure that this (IPv4) code is up to standard and to date, but am 
lacking the required additional time to implement the same for IPv6. 
I am trying to contact people to help with the port, but for the moment I will take 
responsibility only for the IPv4 version.

And if there is someone `well-known and respected' who is interested in taking this code 
over, I would only be happy for him/her to do this. But I won't simply `disappear' :-)







  reply	other threads:[~2006-06-08 20:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 10:50 [PATCH 2.6.17-rc6-mm1 ] net: RFC 3828-compliant UDP-Lite support Gerrit Renker
2006-06-08 11:03 ` YOSHIFUJI Hideaki / 吉藤英明
     [not found]   ` <200606081222.54856.gerrit@erg.abdn.ac.uk>
2006-06-08 18:51     ` David Miller
2006-06-08 11:30 ` YOSHIFUJI Hideaki / 吉藤英明
2006-06-08 14:47 ` Alan Cox
2006-06-08 14:38   ` YOSHIFUJI Hideaki / 吉藤英明
2006-06-08 16:03   ` Gerrit Renker
2006-06-08 18:53     ` David Miller
2006-06-08 19:46       ` James Morris
2006-06-08 20:09         ` Gerrit Renker [this message]
2006-06-08 22:13           ` David Miller
2006-06-09  9:36             ` Gerrit Renker
2006-06-09 13:29               ` YOSHIFUJI Hideaki / 吉藤英明

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=200606082109.34338.gerrit@erg.abdn.ac.uk \
    --to=gerrit@erg.abdn.ac.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kaber@coreworks.de \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pekkas@netcore.fi \
    --cc=yoshfuji@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