From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: dccp@vger.kernel.org
Subject: Re: Test tree patch inventory - update: 3rd batch
Date: Wed, 21 Nov 2007 12:42:14 +0000 [thread overview]
Message-ID: <20071121124214.GC24995@ghostprotocols.net> (raw)
Em Sat, Nov 17, 2007 at 03:42:52PM +0000, Gerrit Renker escreveu:
>
>
> 7. Miscellaneous DCCP updates
> -----------------------------
> The last batch before the begin of the feature-negotiation patch set contains individual,
> standalone patches (and thus ideal for cherry-picking):
>
> [DCCP]: Honour and make use of shutdown option set by user
Applied
> [DCCP]: Update documentation
Applied
> [DCCP]: Promote CCID2 as default CCID
Applied to simplify things for now, but I still think that for some
setups it may be interesting to allow CCID2 not to be built.
> [DCCP]: Remove redundant dependency on IP_DCCP
Applied
> [DCCP]: Ignore Ack Vectors / Elapsed Time on DCCP-Request also
Applied
> [DCCP]: Update documentation on ioctls
Applied
>
> 8. The Feature-Negotiation patch set
> ------------------------------------
> The set splits into several smaller (self-contained) blocks, all documented in this section.
> The first block is distinct from feature negotiation, it only concerns request sockets:
>
> [DCCP]: Allow to parse options on Request Sockets
This one can be folded with the next, I guess, since its only use of
the newly introduce dreq on dccp_parse_options is to test against NULL,
but that could be achieved by checking the packet type.
> [DCCP]: Add (missing) option parsing to request_sock processing
> [DCCP]: Handle timestamps on Request/Response exchange separately
> [DCCP]: Support inserting options during the 3-way handshake
next reply other threads:[~2007-11-21 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 12:42 Arnaldo Carvalho de Melo [this message]
2007-11-21 14:07 ` Test tree patch inventory - update: 3rd batch Gerrit Renker
2007-11-21 14:18 ` Arnaldo Carvalho de Melo
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=20071121124214.GC24995@ghostprotocols.net \
--to=acme@ghostprotocols.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox