9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mk time-check/slice issue
Date: Wed, 18 Dec 2013 22:07:25 -0800	[thread overview]
Message-ID: <20131219060725.7EB64B82A@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 19 Dec 2013 00:40:52 EST." <34270f8ddb3fc06e71d4db496a891dd4@brasstown.quanstro.net>

On Thu, 19 Dec 2013 00:40:52 EST erik quanstrom <quanstro@quanstro.net> wrote:
>                                                     if the point is to
> make mk precise, that goal can be accomplished with a little effort.

I suppose making atime, mtime of type struct timespec would
break too much including 9p?



  reply	other threads:[~2013-12-19  6:07 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 22:01 Blake McBride
2013-12-18 22:08 ` Matthew Veety
2013-12-18 22:42   ` Blake McBride
2013-12-18 22:16 ` erik quanstrom
2013-12-18 22:46   ` Blake McBride
2013-12-19  5:40     ` erik quanstrom
2013-12-19  6:07       ` Bakul Shah [this message]
2013-12-19 10:59         ` Charles Forsyth
2013-12-19 14:21           ` Oleksandr Iakovliev
2013-12-19 14:58             ` erik quanstrom
2013-12-19 14:52       ` Blake McBride
2013-12-19 14:55         ` erik quanstrom
2013-12-19 15:58           ` Blake McBride
2013-12-19 16:30             ` Tristan
2013-12-19 16:37               ` Blake McBride
2013-12-19 16:40                 ` Jacob Todd
2013-12-19 17:05                   ` Blake McBride
2013-12-19 17:24                 ` Tristan
2013-12-19 18:30                   ` Blake McBride
2013-12-19 17:59             ` Steffen Daode Nurpmeso
2013-12-19 17:07         ` a
2013-12-19 18:40           ` Blake McBride
2013-12-19 18:58             ` Kurt H Maier
2013-12-19 19:06             ` Matthew Veety
2013-12-19 19:07             ` Kurt H Maier
2013-12-19 19:20               ` Blake McBride
2013-12-19 19:27                 ` Kurt H Maier
2013-12-19 19:42                   ` Blake McBride
2013-12-19 20:02                     ` Kurt H Maier
2013-12-19 20:18                       ` erik quanstrom
2013-12-19 20:23                         ` Kurt H Maier
2013-12-19 19:35                 ` a
2013-12-19 19:09             ` a
2013-12-27 10:16               ` dexen deVries
2013-12-19 19:09             ` erik quanstrom
2013-12-19 19:29               ` Blake McBride
2013-12-19 19:39                 ` Gabriel Diaz
2013-12-19 20:15                 ` Richard Miller
2013-12-19 20:28                   ` Blake McBride
2013-12-19 20:45                     ` Richard Miller
2013-12-20 15:23                       ` Aram Hăvărneanu
2013-12-19 19:12             ` Skip Tavakkolian
2013-12-19 19:22               ` Blake McBride
2013-12-19 19:43                 ` Rudolf Sykora
2013-12-19 19:58                   ` Blake McBride
2013-12-19 19:26             ` sl
2013-12-19 10:01     ` Richard Miller
2013-12-19 15:01       ` erik quanstrom
     [not found] <CAC0DbM5safEHO_MFpBazvvH6CcGQXGTow-Fe7fkqkP6GrU1Xzw@mail.gmail.com>
     [not found] ` <CAC0DbM7S-xZvOSDwB6KoWH2X8ny_57F9mBE7gaB_BuWR5RSJiw@mail.gmail.com>
2013-12-18 23:09   ` Jason Catena
2013-12-19  5:47     ` erik quanstrom

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=20131219060725.7EB64B82A@mail.bitblocks.com \
    --to=bakul@bitblocks.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).