From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/lib/plumb/basic
Date: Tue, 23 Jul 2002 15:37:27 +0900 [thread overview]
Message-ID: <5734436b598e22af8932a4668e5ede3c@granite.cias.osakafu-u.ac.jp> (raw)
> arg isfile ./$1 /sys/include/$1
This makes damege to the rule, I now understand.
How we can make it work as follows:
1) if there is thread.h in /3e/sys/include, then catch it first.
2) if not, catch /sys/include/thread.h
Kenji
next reply other threads:[~2002-07-23 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 6:37 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-24 0:40 okamoto
2002-07-23 12:29 rob pike, esq.
2002-07-23 6:41 okamoto
2002-07-23 6:24 okamoto
2002-07-23 6:58 ` Lucio De Re
2002-07-23 4:37 rob pike, esq.
2002-07-23 4:07 okamoto
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=5734436b598e22af8932a4668e5ede3c@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).