From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Frans Pop <elendil@planet.nl>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hfsplus: Correct user visible printk
Date: Fri, 2 May 2008 23:29:55 +0100 [thread overview]
Message-ID: <20080502232955.02b1d818@core> (raw)
In-Reply-To: <481B851D.90905@goop.org>
> Prescriptive arguments from authority don't really carry much weight.
> In this case it's particularly weak since Apple refer to hfs as a
> "journaled" or "journaling" filesystem[1].
Indeed.
> And now I've been staring at it for so long that its just turned into a
> weird word...
Rotfl - it's not that important so lets forget about it if it upsets
people so much
next prev parent reply other threads:[~2008-05-02 22:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 13:29 [PATCH] hfsplus: Correct user visible printk Alan Cox
2008-05-02 14:00 ` Frans Pop
2008-05-02 14:04 ` Alan Cox
2008-05-02 15:42 ` Frans Pop
2008-05-02 15:44 ` Alan Cox
2008-05-02 21:18 ` Jeremy Fitzhardinge
2008-05-02 22:29 ` Alan Cox [this message]
2008-05-03 11:49 ` SL Baur
2008-05-03 12:06 ` Frans Pop
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=20080502232955.02b1d818@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=elendil@planet.nl \
--cc=jeremy@goop.org \
--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