From: David Miller <davem@davemloft.net>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 0/7] [DCCP]: Fixes and enhancements
Date: Sun, 27 Aug 2006 04:45:24 +0000 [thread overview]
Message-ID: <20060826.214524.89039745.davem@davemloft.net> (raw)
In-Reply-To: <200608241516.34448.ian.mcdonald@jandi.co.nz>
From: "Ian McDonald" <ian.mcdonald@jandi.co.nz>
Date: Sun, 27 Aug 2006 15:46:58 +1200
> On 8/27/06, David Miller <davem@davemloft.net> wrote:
> > >
> > > I would love 3, 4, 5 to go into 2.6.18 as these resolve long standing CCID3
> > > issues that have been in the DCCP tree since inception and have caught a
> > > number of people.
> >
> > Ok, I'll toss 1-5 into 2.6.18
>
> Thanks for that. Are 6 and 7 going into 2.6.19 or do you want Arnaldo
> to have a bit more of a look? 6 in particular is trivial.
Those patches are already in net-2.6.19
> Basically the implementation in the DCCP code was buggy and was
> transmitting too fast so I have made it conform to the RFC much
> closer.
Thanks for the explanation.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: ian.mcdonald@jandi.co.nz
Cc: a.bittau@cs.ucl.ac.uk, arnaldo.melo@gmail.com,
dccp@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/7] [DCCP]: Fixes and enhancements
Date: Sat, 26 Aug 2006 21:45:24 -0700 (PDT) [thread overview]
Message-ID: <20060826.214524.89039745.davem@davemloft.net> (raw)
In-Reply-To: <5640c7e00608262046x598d873cr7a4bcd2df971dac0@mail.gmail.com>
From: "Ian McDonald" <ian.mcdonald@jandi.co.nz>
Date: Sun, 27 Aug 2006 15:46:58 +1200
> On 8/27/06, David Miller <davem@davemloft.net> wrote:
> > >
> > > I would love 3, 4, 5 to go into 2.6.18 as these resolve long standing CCID3
> > > issues that have been in the DCCP tree since inception and have caught a
> > > number of people.
> >
> > Ok, I'll toss 1-5 into 2.6.18
>
> Thanks for that. Are 6 and 7 going into 2.6.19 or do you want Arnaldo
> to have a bit more of a look? 6 in particular is trivial.
Those patches are already in net-2.6.19
> Basically the implementation in the DCCP code was buggy and was
> transmitting too fast so I have made it conform to the RFC much
> closer.
Thanks for the explanation.
next prev parent reply other threads:[~2006-08-27 4:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 3:16 [PATCH 0/7] [DCCP]: Fixes and enhancements Ian McDonald
2006-08-24 3:16 ` Ian McDonald
2006-08-24 11:59 ` David Miller
2006-08-24 11:59 ` David Miller
2006-08-24 18:09 ` Ian McDonald
2006-08-24 18:09 ` Ian McDonald
2006-08-25 13:19 ` Arnaldo Carvalho de Melo
2006-08-25 13:19 ` Arnaldo Carvalho de Melo
2006-08-27 2:08 ` David Miller
2006-08-27 2:08 ` David Miller
2006-08-27 3:46 ` Ian McDonald
2006-08-27 3:46 ` Ian McDonald
2006-08-27 4:45 ` David Miller [this message]
2006-08-27 4:45 ` David Miller
2006-08-27 4:57 ` Ian McDonald
2006-08-27 4:57 ` Ian McDonald
2006-08-27 5:39 ` David Miller
2006-08-27 5:39 ` David Miller
2006-08-27 6:18 ` Ian McDonald
2006-08-27 6:18 ` Ian McDonald
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=20060826.214524.89039745.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dccp@vger.kernel.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.