public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: how to track down strange bug
Date: Thu, 19 Oct 2006 20:51:51 +0000 (UTC)	[thread overview]
Message-ID: <eh8oh6$cbe$4@sea.gmane.org> (raw)
In-Reply-To: 45374742.4010604@gmx.at

"Florian D." <flockmock@gmx.at> posted 45374742.4010604@gmx.at, excerpted
below, on  Thu, 19 Oct 2006 11:37:06 +0200:

>> I've had all those problems at one time or another.
> would be boring without it, no? ;)

Indeed. =8^)  Part of the reason Linux (and computers in general) remain
interesting to me is the challenge of figuring out what went wrong and
fixing it.  I don't find my freezer or microwave near this interesting,
because they "just work". =8^)  It'd be like watching grass grow or paint
dry.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



  parent reply	other threads:[~2006-10-19 20:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 22:30 [gentoo-amd64] how to track down strange bug Florian D.
2006-10-18 23:46 ` Peter Davoust
2006-10-19  0:35 ` [gentoo-amd64] " Duncan
2006-10-19  9:37   ` Florian D.
2006-10-19 10:27     ` Rob Lesslie
2006-10-19 20:51     ` Duncan [this message]
2006-10-19 22:48       ` Neil Bothwick
2006-10-20 10:41         ` Duncan
2006-10-20 11:09           ` Neil Bothwick
2006-10-20 11:39             ` Duncan
2006-10-20 15:02             ` Paul de Vrieze
2006-10-20 15:11               ` Rob Lesslie
2006-10-20 15:25               ` Neil Bothwick
2006-10-20 14:58 ` [gentoo-amd64] " Paul de Vrieze

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='eh8oh6$cbe$4@sea.gmane.org' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /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