From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <40711c3657e4203ed90a91ab770b3380@plug.quanstro.net>
References: <AANLkTinwmuP0RjYz=FsFZQwOCBmj=sUurSJbC70BuDav@mail.gmail.com>
	<40711c3657e4203ed90a91ab770b3380@plug.quanstro.net>
Date: Fri,  7 Jan 2011 11:51:56 +0200
Message-ID: <AANLkTikEqb08gAGnkHbC0XosnOyqi==vRZVgQ1hpftVx@mail.gmail.com>
From: Ciprian Dorin Craciun <ciprian.craciun@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] mk (from plan9ports) modification time resolution issue?
Topicbox-Message-UUID: 91366ddc-ead6-11e9-9d60-3106f5b1d025

On Fri, Jan 7, 2011 at 11:25, erik quanstrom <quanstro@quanstro.net> wrote:
> the code has its reasons. =C2=A0from mk.c:/^outofdate
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/*
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 * Treat equal tim=
es as out-of-date.
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 * It's a race, an=
d the safer option is to do
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 * extra building =
rather than not enough.
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 */
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0return node->time =
<=3D arc->n->time;
>
> - erik


    :) I've kind of feared that this is the reason... :)

    But still how do people handle the issue?