From: Jack Johnson <knapjack@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9atom
Date: Fri, 4 Jan 2013 10:31:37 -0900 [thread overview]
Message-ID: <CAJd0wvDkaaZzNFfnWyTnA+3iA3k9R+0xKS1JeLXVoD6J2A0U7g@mail.gmail.com> (raw)
In-Reply-To: <6e680bde0bcfb96fa20d42f2371e075f@hamnavoe.com>
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
On Jan 4, 2013 10:07 AM, "Richard Miller" <9fans@hamnavoe.com> wrote:
>
> > It contains the full file system from the Plan 9 CD image,
> > unmodified, except a single line change in the kernel binary.
>
> I can't contain my curiosity: what's the line?
>
> I once worked with a colleague who had a superstition that any
> one-line change to production software was almost certain to
> introduce a bug. (Actually what he said was "one-card change",
> which indicates how long ago this was.) If he had to make
> a modification simple enough to be done in one line, he would
> always combine it with some other random harmless change like
> renaming a variable.
It's funny, if you were correcting someone else's bug unknowingly
introduced by a one-line change your fix could justifiably be one line, but
then you would think the odds of it reoccurring in the future would be
non-zero, and you might as well add a comment for future fumblers. :)
-Jack
[-- Attachment #2: Type: text/html, Size: 1210 bytes --]
next prev parent reply other threads:[~2013-01-04 19:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 3:50 erik quanstrom
2013-01-03 8:17 ` Bence Fábián
2013-01-04 9:37 ` faif
2013-01-04 16:19 ` erik quanstrom
2013-01-04 16:27 ` John Floren
2013-01-04 16:35 ` Aram Hăvărneanu
2013-01-04 16:39 ` Rox 64
2013-01-04 17:26 ` John Floren
2013-01-04 17:41 ` John Floren
2013-01-04 18:48 ` David du Colombier
2013-01-04 19:05 ` Richard Miller
2013-01-04 19:22 ` David du Colombier
2013-01-04 19:44 ` erik quanstrom
2013-01-04 20:08 ` David du Colombier
2013-01-04 20:27 ` Bakul Shah
2013-01-04 20:36 ` erik quanstrom
2013-01-04 20:59 ` Bakul Shah
2013-01-05 2:21 ` erik quanstrom
2013-01-05 20:07 ` Rox 64
2013-01-05 20:10 ` Rox 64
2013-01-05 21:13 ` David du Colombier
2013-01-05 22:42 ` Rox 64
2013-01-05 23:25 ` John Floren
2013-01-05 23:36 ` Jacob Todd
2013-01-05 23:43 ` Rox 64
2013-01-05 23:56 ` John Floren
2013-01-06 0:29 ` Rox 64
2013-01-06 0:55 ` Rox 64
2013-01-06 1:05 ` Matthew Veety
2013-01-06 14:24 ` Rox 64
2013-01-06 14:28 ` erik quanstrom
2013-01-06 16:49 ` Rox 64
2013-01-06 17:34 ` John Floren
2013-01-04 19:31 ` Jack Johnson [this message]
2013-01-04 19:35 ` erik quanstrom
2013-01-04 19:50 ` Rox 64
2013-01-04 20:03 ` Matthew Veety
2013-01-04 20:24 ` erik quanstrom
2013-01-04 20:33 ` Rox 64
2013-01-04 22:13 ` David du Colombier
2013-01-04 20:55 ` Matthew Veety
2013-01-04 17:49 ` erik quanstrom
2013-01-04 18:46 ` David du Colombier
2013-01-04 16:34 ` Richard Miller
2013-01-04 17:58 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2013-03-01 14:11 erik quanstrom
2011-11-21 20:13 erik quanstrom
2011-05-07 2:57 erik quanstrom
2011-05-16 14:41 ` Steve Simon
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=CAJd0wvDkaaZzNFfnWyTnA+3iA3k9R+0xKS1JeLXVoD6J2A0U7g@mail.gmail.com \
--to=knapjack@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).