| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH] xfs: Update mount options documentation |
| From: | Carlos Maiolino <cmaiolino@xxxxxxxxxx> |
| Date: | Thu, 18 Oct 2012 14:04:42 -0300 |
| In-reply-to: | <508028CC.5080800@xxxxxxx> |
| Mail-followup-to: | xfs@xxxxxxxxxxx |
| References: | <1350574138-30305-1-git-send-email-cmaiolino@xxxxxxxxxx> <5080253A.9060906@xxxxxxx> <5080279C.8030702@xxxxxxxxxxxxxxxxx> <508028CC.5080800@xxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@xxxxxxxxxxx > >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@xxxxxxxxxxx > http://oss.sgi.com/mailman/listinfo/xfs -- --Carlos |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH v5 06/10] xfs: add XFS_IOC_FREE_EOFBLOCKS ioctl, Brian Foster |
|---|---|
| Next by Date: | Re: [PATCH] xfs: Update mount options documentation, Mark Tinguely |
| Previous by Thread: | Re: [PATCH] xfs: Update mount options documentation, Mark Tinguely |
| Next by Thread: | Re: [PATCH] xfs: Update mount options documentation, Mark Tinguely |
| Indexes: | [Date] [Thread] [Top] [All Lists] |