public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Christopher Swingley <cswingle@iarc.uaf.edu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Oops during mkfs, SMP Opteron, 2.6.8.1 / -mm4
Date: Mon, 23 Aug 2004 19:13:24 -0400	[thread overview]
Message-ID: <1093302804.826.37.camel@krustophenia.net> (raw)
In-Reply-To: <20040823225426.GE2519@iarc.uaf.edu>

On Mon, 2004-08-23 at 18:54, Christopher Swingley wrote:

> I know it's bad form to reply to one's own posting, but I suspect that 
> more information is probably useful here.
> 

Not on LKML it's not.  If you report a problem, then discover more
information about it, this is the recommended way.  What is considered
bad form is starting a new thread in this situation.

Lee


      reply	other threads:[~2004-08-23 23:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23 18:12 Oops during mkfs, SMP Opteron, 2.6.8.1 / -mm4 Christopher Swingley
2004-08-23 22:54 ` Christopher Swingley
2004-08-23 23:13   ` Lee Revell [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=1093302804.826.37.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=cswingle@iarc.uaf.edu \
    --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