9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio buglet
Date: Mon, 14 Aug 2006 13:57:58 -0500	[thread overview]
Message-ID: <3dfcd91da2625bfd201d74ce3b498d9a@quanstro.net> (raw)
In-Reply-To: <200608141853.k7EIrqA25216@zamenhof.cs.utwente.nl>

i think that it's a timing issue.

- erik

On Mon Aug 14 13:54:30 CDT 2006, Axel.Belinfante@cs.utwente.nl wrote:
> on a system that has not been updated for a while i could
> not reproduce the problem (or I did not understand how to do it).
> 
> diff showed changes in rio.c and wind.c, the following updates i 'missed'.
> hope this may help tracking it down.
> 
> Axel.


  reply	other threads:[~2006-08-14 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 11:14 Steve Simon
2006-08-14 11:44 ` erik quanstrom
2006-08-14 18:53   ` Axel Belinfante
2006-08-14 18:57     ` erik quanstrom [this message]
2006-08-14 19:30       ` "Nils O. Selåsdal"
2006-08-14 18:04 ` Sascha Retzki

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=3dfcd91da2625bfd201d74ce3b498d9a@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).