From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>, "Arkadiusz Miśkiewicz" <arekm@maven.pl>
Subject: projid32bit=1 default in xfsprogs-3.2.0
Date: Mon, 14 Oct 2013 11:30:13 -0500 [thread overview]
Message-ID: <525C1C15.7020204@sandeen.net> (raw)
The commit:
f3edb66a mkfs.xfs: validate options for CRCs up front.
unintentionally (?) defaulted to projid32bit=1 for all filesystems
at mkfs time.
Support for 32 bit project IDs has been present since kernel v2.6.37.
Is everybody ok with making this change for 3.2.0? Speak now or
forever hold your peace, as they say.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-10-14 16:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 16:30 Eric Sandeen [this message]
2013-10-14 21:16 ` projid32bit=1 default in xfsprogs-3.2.0 Dave Chinner
2013-10-14 21:23 ` Ben Myers
2013-10-14 21:24 ` Eric Sandeen
2013-10-15 19:46 ` Christoph Hellwig
2013-10-15 20:43 ` Christoph Hellwig
2013-10-15 21:22 ` Ben Myers
2013-10-15 21:31 ` Christoph Hellwig
2013-10-15 21:49 ` Ben Myers
2013-10-15 21:57 ` Eric Sandeen
2013-10-15 22:48 ` Dave Chinner
2013-10-15 22:59 ` Eric Sandeen
2014-01-10 14:45 ` Rich Johnston
2014-01-11 10:30 ` Christoph Hellwig
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=525C1C15.7020204@sandeen.net \
--to=sandeen@sandeen.net \
--cc=arekm@maven.pl \
--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