From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] writing to ctl using fprint and write
Date: Thu, 29 Jul 2010 11:04:30 -0400 [thread overview]
Message-ID: <764fc0b0ab4cc1f9a890bc61a61a7c81@ladd.quanstro.net> (raw)
In-Reply-To: <460c4983c43135098e3c1f2b36623833@swcp.com>
> Thanks Erik, Sape, and Skip. That was such a STUPID error, and I thank
> you all for the extra eyes. I think it is time for a break and a bowl of
> tea...
relax. not stupid, subtle. it takes vigilance to keep
sizeof, nelem, strlen, and the number of characters
straight.
- erik
next prev parent reply other threads:[~2010-07-29 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 12:02 EBo
2010-07-29 12:06 ` erik quanstrom
2010-07-29 13:21 ` EBo
2010-07-29 15:04 ` erik quanstrom [this message]
2010-07-29 15:11 ` David Leimbach
2010-07-29 23:42 ` Federico G. Benavento
2010-07-29 15:18 ` Brian L. Stuart
2010-07-29 15:27 ` EBo
2010-07-29 12:07 ` Skip Tavakkolian
2010-07-29 12:12 ` Sape Mullender
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=764fc0b0ab4cc1f9a890bc61a61a7c81@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).