From: "Rob 'Commander' Pike" <r@google.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in libcomplete?
Date: Sat, 14 Feb 2004 11:01:24 -0800 [thread overview]
Message-ID: <b5e04e90f3540c56ba8015a4bb4183ed@google.com> (raw)
that's embarrassing. let's close it.
-rob
libcomplete%% diff complete.c /sys/src/libcomplete
61,62c61
< if(n <= 0){
< close(fd);
---
> if(n <= 0)
64d62
< }
139d136
< close(fd);
next reply other threads:[~2004-02-14 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 19:01 Rob 'Commander' Pike [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-14 15:15 andrey mirtchovski
2004-02-14 16:35 ` Rob Pike
2004-02-14 16:49 ` David Presotto
2004-02-14 18:18 ` andrey mirtchovski
2004-02-14 17:56 ` andrey mirtchovski
2004-02-14 19:09 ` Rob Pike
2004-02-14 21:57 ` boyd, rounin
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=b5e04e90f3540c56ba8015a4bb4183ed@google.com \
--to=r@google.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).