From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: TCP/IP memory leaks
Date: Mon, 6 Feb 1995 11:59:03 -0500 [thread overview]
Message-ID: <19950206165903.oubMnQTUQRVb09AZPmAPBzj5FUQCYO9OnAsywI2UeUU@z> (raw)
>>The point of the code freeze is to fix bugs just like this, I encourage you
>>to submit them to linux and/or whoever is in charge of the code.
i do not think that Linus, however keen, will make much use of diffs to Plan 9,
unless i include a lot of context!
next reply other threads:[~1995-02-06 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-02-06 16:59 forsyth [this message]
1995-02-06 18:22 Bill
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=19950206165903.oubMnQTUQRVb09AZPmAPBzj5FUQCYO9OnAsywI2UeUU@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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).