From: Bengt Kleberg <eleberg@cbe.ericsson.se>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mk surprises me
Date: Thu, 28 Mar 2002 09:01:07 +0100 [thread overview]
Message-ID: <200203280801.g2S817U21452@cbe.ericsson.se> (raw)
> Delivered-To: 9fans@cse.psu.edu
> X-Authentication-Warning: copernicus.cs.utwente.nl: belinfan@localhost didn't
use HELO protocol
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] mk surprises me
> From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
...deleted
> I tried your example on plan 9 mk, and it seemed to work as expected.
just to check 'work as expected':
the recipe was done (cp f1.c f1), even when f1.c was older than f1,
provided that hdr.h was younger than f1?
bengt
next reply other threads:[~2002-03-28 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 8:01 Bengt Kleberg [this message]
2002-03-28 10:50 ` Axel Belinfante
2002-03-28 11:04 ` William Josephson
-- strict thread matches above, loose matches on Subject: below --
2002-04-02 7:49 Bengt Kleberg
2002-03-28 14:52 David Gordon Hogan
2002-03-28 8:17 Bengt Kleberg
2002-03-27 14:10 forsyth
2002-03-27 13:10 Bengt Kleberg
2002-03-27 13:40 ` Axel Belinfante
2002-03-27 13:56 ` Axel Belinfante
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=200203280801.g2S817U21452@cbe.ericsson.se \
--to=eleberg@cbe.ericsson.se \
--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).