9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mk surprises me
Date: Wed, 27 Mar 2002 14:56:21 +0100	[thread overview]
Message-ID: <200203271356.g2RDuMp24734@copernicus.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Wed, 27 Mar 2002 14:40:45 +0100." <200203271340.g2RDekt13862@copernicus.cs.utwente.nl>

Ok, my previous response was widely off the mark,
 I guess, so, just to make up for it:

I tried your example on plan 9 mk, and it seemed to work as expected.
Now I'll step back for those more knowledgeable...
(and will have some more coffee)

Axel.



  reply	other threads:[~2002-03-27 13:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27 13:10 Bengt Kleberg
2002-03-27 13:40 ` Axel Belinfante
2002-03-27 13:56   ` Axel Belinfante [this message]
2002-03-27 14:10 forsyth
2002-03-28  8:01 Bengt Kleberg
2002-03-28 10:50 ` Axel Belinfante
2002-03-28 11:04   ` William Josephson
2002-03-28  8:17 Bengt Kleberg
2002-03-28 14:52 David Gordon Hogan
2002-04-02  7:49 Bengt Kleberg

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=200203271356.g2RDuMp24734@copernicus.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --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).