public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Maiolino <cmaiolino@redhat.com>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: Update mount options documentation
Date: Thu, 18 Oct 2012 14:04:42 -0300	[thread overview]
Message-ID: <20121018170442.GA6634@andromeda.usersys.redhat.com> (raw)
In-Reply-To: <508028CC.5080800@sgi.com>

On Thu, Oct 18, 2012 at 11:05:32AM -0500, Mark Tinguely wrote:
> On 10/18/12 11:00, Dave Howorth wrote:
> >Mark Tinguely wrote:
> >>Would "Indicates that XFS is allowed to create inodes at locations up to
> >>32 bits of significance .."
> >
> >I prefer the original wording. Your suggestion says something about what
> >XFS can do, but nothing about what it is not allowed to do, which is
> >rather more important.
> >
> >_______________________________________________
> >xfs mailing list
> >xfs@oss.sgi.com
> >http://oss.sgi.com/mailman/listinfo/xfs
> 
> I see your point. Sounds good to me.
> 
> --Mark.
> 
This means no change is needed?

> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

-- 
--Carlos

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-10-18 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 15:28 [PATCH] xfs: Update mount options documentation Carlos Maiolino
2012-10-18 15:50 ` Mark Tinguely
2012-10-18 16:00   ` Dave Howorth
2012-10-18 16:05     ` Mark Tinguely
2012-10-18 17:04       ` Carlos Maiolino [this message]
2012-10-18 17:15         ` Mark Tinguely
2012-10-18 18:40           ` Carlos Maiolino
2012-11-08 17:47             ` Ben Myers

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=20121018170442.GA6634@andromeda.usersys.redhat.com \
    --to=cmaiolino@redhat.com \
    --cc=xfs@oss.sgi.com \
    /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