From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] yet another 9load change
Date: Thu, 22 May 2003 16:10:58 +0200 [thread overview]
Message-ID: <fbf8bef58c5a464f4752d358013fbcab@plan9.escet.urjc.es> (raw)
I changed 9load to use snprint instead of sprint and enforce limits in
a couple of places. The changed files (which still includes the
[$var] thing) are at /n/sources/export/nemo/sys/src/boot/pc and can be
pulled using replica.
If you are interested just in the safety changes (buf. limits), you can
diff those files wrt the distributed ones, and apply just them.
hth
reply other threads:[~2003-05-22 14:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fbf8bef58c5a464f4752d358013fbcab@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).