From: Blake McBride <blake@mcbride.name>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mk time-check/slice issue
Date: Thu, 19 Dec 2013 13:58:53 -0600 [thread overview]
Message-ID: <CABwHSOt-bpw9g1gX15-80XQ4GsDJG7RY4XLSzW-X=aX_sKhebQ@mail.gmail.com> (raw)
In-Reply-To: <CAOEdRO0CE7aNAtdoni3mvkoiyQjyhMF+9DPVOfTgm7=uZX6FsA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
On Thu, Dec 19, 2013 at 1:43 PM, Rudolf Sykora <rudolf.sykora@gmail.com>wrote:
> Hello,
>
> On 19 December 2013 20:22, Blake McBride <blake@mcbride.name> wrote:
> > Agreed. I enjoy reasoned debate. I don't enjoy being told the reason is
> > because "that's the way we do it". That is not reasoned debate. It is
> club
> > support.
>
> I believe, from reading this mailing list for some time, you must be ready
> to find many stupid reasonings. But opposite is, fortunately, also true:
> there
> are people here who can help.
>
> Second, you bumped into something which is not 100% to your liking, but on
> the other hand is "simple" and works. The simplicity is, in my
> opinion, what has always
> counted for people seriously-involved in plan9 and is one of the main
> advantages of the plan9 programs.
>
> Third, it would be, from my experience, an error to expect that there are
> no
> errors/flaws in the plan9 programs. When I started to play with plan9,
> I thought:
> it is simple, there are no errors. But in reality, whatever I tried,
> it did not quite
> work. So, my advice is to be ready to find such problems nearly all the
> time.
> And since many people who created the programs are gone by now, there is
> often little effort to correct these, even if there are true bugs.
>
> That's what I think.
>
> Ruda
>
>
Thanks for your thoughtful input!
Unfortunately, I have started and continue to provoke a most unhelpful line
of discussion. Know that it was (poorly) done with good intention
merely to draw a distinction between technical reasons and "that's the way
we do it" attitudes.
Blake
[-- Attachment #2: Type: text/html, Size: 3703 bytes --]
next prev parent reply other threads:[~2013-12-19 19:58 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
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 [this message]
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='CABwHSOt-bpw9g1gX15-80XQ4GsDJG7RY4XLSzW-X=aX_sKhebQ@mail.gmail.com' \
--to=blake@mcbride.name \
--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).