All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: omb@bluewin.ch
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to be (SAFE) a kernel developer ?
Date: Wed, 20 Jul 2005 02:25:41 +0200	[thread overview]
Message-ID: <9a87484905071917256e3b71cf@mail.gmail.com> (raw)
In-Reply-To: <42DD7644.5040304@khandalf.com>

On 7/19/05, Brian O'Mahoney <omb@khandalf.com> wrote:
> 
> To:	unlisted-recipients:; (no To-header on input) 
            ^^^
             That's a bad habbit - makes it impossible to send a
proper reply back to all the recipients. LKML is a public list, please
use To: and CC: so it's possible to reply to the proper people, and
don't trim the CC: list please.


> Jesper Juhl wrote: ...
> 
> much useful advice, almost all of which I agree with _BUT_
> 
> please do NOT debug kernel mods on your 'main-box', where your
> filesystems live. unless you like to live dangerously and make
> perfect backups you don't mind spending lots of hours restoring,
> 
You are right. A sacrificial box or at least proper backups of any
important stuff is important. I didn't write that since I figured it
to be obvious, but I guess I should have spelled it out anyway. Thank
you for making that bit clear :-)


-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

      parent reply	other threads:[~2005-07-20  0:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18 14:35 how to be a kernel developer ? regatta
2005-07-18 14:43 ` Alejandro Bonilla
2005-07-18 16:22   ` Andrew Ruder
2005-07-19  1:11 ` Jesper Juhl
2005-07-19  1:24   ` Jesper Juhl
2005-07-19 21:53   ` how to be (SAFE) " Brian O'Mahoney
2005-07-19 23:02     ` Jan Blunck
2005-07-20  0:25     ` Jesper Juhl [this message]

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=9a87484905071917256e3b71cf@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=omb@bluewin.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.