From: Ciprian Dorin Craciun <ciprian.craciun@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mk (from plan9ports) modification time resolution issue?
Date: Fri, 7 Jan 2011 11:51:56 +0200 [thread overview]
Message-ID: <AANLkTikEqb08gAGnkHbC0XosnOyqi==vRZVgQ1hpftVx@mail.gmail.com> (raw)
In-Reply-To: <40711c3657e4203ed90a91ab770b3380@plug.quanstro.net>
On Fri, Jan 7, 2011 at 11:25, erik quanstrom <quanstro@quanstro.net> wrote:
> the code has its reasons. from mk.c:/^outofdate
>
> /*
> * Treat equal times as out-of-date.
> * It's a race, and the safer option is to do
> * extra building rather than not enough.
> */
> return node->time <= arc->n->time;
>
> - erik
:) I've kind of feared that this is the reason... :)
But still how do people handle the issue?
next prev parent reply other threads:[~2011-01-07 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 9:13 Ciprian Dorin Craciun
2011-01-07 9:25 ` erik quanstrom
2011-01-07 9:51 ` Ciprian Dorin Craciun [this message]
2011-01-07 10:40 ` Henning Schild
2011-01-13 19:36 ` Ciprian Dorin Craciun
2011-01-18 16:28 ` Russ Cox
2011-01-18 18:24 ` Ciprian Dorin Craciun
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='AANLkTikEqb08gAGnkHbC0XosnOyqi==vRZVgQ1hpftVx@mail.gmail.com' \
--to=ciprian.craciun@gmail.com \
--cc=9fans@9fans.net \
/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).