From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in fmtfmt
Date: Mon, 15 Jul 2002 14:55:13 -0400 [thread overview]
Message-ID: <011d2d3398b7dc63c4ba13066bb463b3@plan9.bell-labs.com> (raw)
> There is a bug in fmtfmt.
Indeed there was. I was being clever and then getting it wrong.
I have rewritten it to be less clever and more likely to be right.
Updated /sys/src/libc/fmt/fmt.c and /386/lib/libc.a on sources.
-rob
next reply other threads:[~2002-07-15 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 18:55 rob pike, esq. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-15 9:31 Saroj Mahapatra
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=011d2d3398b7dc63c4ba13066bb463b3@plan9.bell-labs.com \
--to=rob@plan9.bell-labs.com \
--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).