From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] udp headers
Date: Fri, 18 Apr 2003 14:01:31 +0100 [thread overview]
Message-ID: <3f64b3f4a21544170f3f2dcea1a256a9@9fs.org> (raw)
In-Reply-To: <d82982ea633d663fe7e528f285444d61@plan9.bell-labs.com>
> My first reaction is to just change the definition of Udphdr and
> Udphdrsize and get everyone to recompile everything. While I'm
> at it maybe I should toss in whatever else people want to see:
>
> its used). While I'm at it, I'll nuke headers4.
>
> Comments? Anyone mind if I break udp headers? I'll update
> everything on sources but you'll have to take care of your own
> programs.
Go ahead, make my day.
next prev parent reply other threads:[~2003-04-18 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 5:58 nigel
2003-04-18 11:50 ` David Presotto
2003-04-18 11:57 ` nigel
2003-04-18 12:24 ` David Presotto
2003-04-18 13:01 ` nigel [this message]
2003-04-29 13:26 ` Boyd Roberts
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=3f64b3f4a21544170f3f2dcea1a256a9@9fs.org \
--to=nigel@9fs.org \
--cc=9fans@cse.psu.edu \
/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).