From: David Ford <david+cert@blue-labs.org>
To: Thunder from the hill <thunder@ngforever.de>
Cc: Jacob Luna Lundberg <kernel@gnifty.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-pre10-ac2, compile warnings/failures
Date: Mon, 10 Jun 2002 23:05:54 -0400 [thread overview]
Message-ID: <3D056912.60104@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0206101920330.17269-100000@hawkeye.luckynet.adm>
My choice was to drop the \n, I don't like very short statements spread
over multiple lines especially if I'm grepping for things.
That's why I chose not to include a \n.
-d
Thunder from the hill wrote:
>Hi,
>
>On Mon, 10 Jun 2002, Jacob Luna Lundberg wrote:
>
>
>>On Mon, 10 Jun 2002, Thunder from the hill wrote:
>>
>>
>>>- printk(KERN_WARNING "i2o: Could not quiesce %s." "
>>>- Verify setup on next system power up.\n", c->name);
>>>+ printk(KERN_WARNING "i2o: Could not quiesce %s."
>>>+ "Verify setup on next system power up.\n",
>>>+ c->name);
>>>
>>>
>>Don't we lose a \n if you do that? Speaking of, is "\n" better, or " "
>>I wonder... ;)
>>
>>
>
>You're right, here comes the accurate version:
>
>
>
next prev parent reply other threads:[~2002-06-11 3:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0206101811180.364-100000@inbetween.blorf.net>
2002-06-11 1:22 ` 2.4.19-pre10-ac2, compile warnings/failures Thunder from the hill
2002-06-11 3:05 ` David Ford [this message]
2002-06-10 21:23 David Ford
2002-06-11 0:59 ` Thunder from the hill
2002-06-11 6:03 ` Greg KH
2002-06-11 14:15 ` David Ford
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=3D056912.60104@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=kernel@gnifty.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@ngforever.de \
/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.