mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Hugh Dickins <hugh@veritas.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	trivial@kernel.org
Subject: Re: [PATCH] FS: Label tmpfs Kconfig option with "tmpfs".
Date: Mon, 7 Jul 2008 18:47:58 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0807071846520.9951@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0807072231160.1608@blonde.site>

On Mon, 7 Jul 2008, Hugh Dickins wrote:

> On Mon, 7 Jul 2008, Robert P. J. Day wrote:
> >
> > Make it clear that the Kconfig option refers to "tmpfs".
> >
> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> It's so long since I used anything but "make oldconfig", which
> already shows TMPFS, making your mod seem redundant.  But you're right,
> menuconfig and xconfig don't show it, so your change is a good one.
>
> Though for the moment I can only give you
> acked-by: hugh dickins <hugh@veritas.com>:
> the next entry is for "Tmpfs POSIX Access Control Lists"
> so I'd rather you say "Tmpfs support (virtual memory file system)",
> then you can uppercase my ack.

or i could change the next line to read "tmpfs" rather than "Tmpfs".
:-)  does anyone have any strong feelings either way?

rday
--


========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

      reply	other threads:[~2008-07-07 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07 19:18 Robert P. J. Day
2008-07-07 21:41 ` Hugh Dickins
2008-07-07 22:47   ` Robert P. J. Day [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=alpine.LFD.1.10.0807071846520.9951@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@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®