From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] mk time-check/slice issue
Date: Thu, 19 Dec 2013 14:09:28 -0500 [thread overview]
Message-ID: <0d962f373ebb1452e3504be85d26b7dd@coraid.com> (raw)
In-Reply-To: <CABwHSOs0TRSw6fF8Kd_Ww6Vdb5K=OSgxZ-kszpZ2c639Fw0oyA@mail.gmail.com>
> What I am beginning to understand from comments like this is that there is
> a "club Plan-9". Everything ever done by the originators of "club Plan-9"
> is correct, period. No mater what exceptions, special cases, or good new
> ideas occur, they are wrong and we will find some way of rationalizing
> "club Plan-9". Anyone can join "club Plan-9" if you buy into that
> assumption. The main purpose of Plan-9 forks (with some exceptions) is to
> port to new hardware. Messing with the premise of "club Plan-9" is
> significantly frowned upon and attacked.
>
> Just a newbie's (with 35 years experience) perception.
first things first. breaking mk is not a good idea. to see that things could
break with < rather than <= one only needs to consider a dependency that might
be modified more than once during a build. for example fu.h that is modified
for a debug version built along a non-debug version.
perhaps there is some truth to this. certainly plan 9 is not perfect. and
certainly there are things you will improve. but on the other hand, many
of us have quite a bit of experience, too.
- erik
next prev parent reply other threads:[~2013-12-19 19:09 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
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 [this message]
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=0d962f373ebb1452e3504be85d26b7dd@coraid.com \
--to=quanstro@labs.coraid.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).