From: Radoslaw "AstralStorm" Szkodzinski <astralstorm@gorzow.mm.pl>
To: Adrian Bunk <bunk@stusta.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc3-mm3 question
Date: Fri, 29 Jul 2005 02:50:34 +0200 [thread overview]
Message-ID: <20050729025034.2b58d34e.astralstorm@gorzow.mm.pl> (raw)
In-Reply-To: <20050728204238.GC4790@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
On Thu, 28 Jul 2005 22:42:38 +0200
Adrian Bunk <bunk@stusta.de> wrote:
> I'm surprised that you are that much concerned about compile errors when
> using a kernel that might regularly exchange the contents of /dev/hda
> and /dev/null .
>
These bugs don't happen too often in reality.
Just please don't be malicious and add this kind of code deliberately. :)
Every build breaker wastes my precious time to fix it.
That's compulsive/obsessive in some way. ;)
On the contrary, my "just break it" desktop is destined to have
it's HDD contents overwritten once in a time.
That's what these spare disks/computers are for, aren't they?
All the data on that computer is volatile, all (not too frequent) backup is
mostly made through the network and checked from the stable computer.
If I really needed it very stable, I wouldn't test Reiser4 on it, less so
a development kernel. That's why my stable machine uses latest release kernel,
and only after it's broken in by at least a week.
--
AstralStorm
GPG Key ID = 0xD1F10BA2
GPG Key fingerprint = 96E2 304A B9C4 949A 10A0 9105 9543 0453 D1F1 0BA2
Please encrypt if you can.
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2005-07-29 0:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 17:43 Radoslaw AstralStorm Szkodzinski
2005-07-28 17:55 ` Andrew Morton
2005-07-28 18:31 ` Radoslaw AstralStorm Szkodzinski
2005-07-28 20:42 ` Adrian Bunk
2005-07-29 0:50 ` Radoslaw AstralStorm Szkodzinski [this message]
2005-07-29 10:57 ` Adrian Bunk
2005-07-29 6:55 ` Matthias Urlichs
2005-07-30 8:39 Chuck Ebbert
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=20050729025034.2b58d34e.astralstorm@gorzow.mm.pl \
--to=astralstorm@gorzow.mm.pl \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®