linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42986] ext2_fs.h requires undefined type umode_t
Date: Sat, 24 Mar 2012 14:04:35 GMT	[thread overview]
Message-ID: <201203241404.q2OE4ZuN024107@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42986-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=42986


Theodore Tso <tytso@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@mit.edu




--- Comment #1 from Theodore Tso <tytso@mit.edu>  2012-03-24 14:04:34 ---
Why do you need ext2_fs.h?   We're planning on removing ext2_fs.h as an
exported header file very shortly (perhaps as soon as v3.4; it's already in Al
Viro's VFS git tree).

Ext 2/3/4 userspace programs ***really*** should be using libext2fs, and if for
some reason they don't want to do that, they can use the ext2_fs.h header file
that is shipped with e2fsprogs and libext2fs.

Programs written as much as 8 years ago and which used libext2fs generally were
able to support ext4 file systems have generally been able to support ext4;
that's one of the major reasons why I strongly suggest the use of that library,
instead of trying to use kernel header files to roll your own thing....

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  reply	other threads:[~2012-03-24 14:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 13:23 [Bug 42986] New: ext2_fs.h requires undefined type umode_t bugzilla-daemon
2012-03-24 14:04 ` bugzilla-daemon [this message]
2012-03-24 14:16 ` [Bug 42986] " bugzilla-daemon
2012-03-25  1:20 ` bugzilla-daemon
2012-03-25  2:47 ` bugzilla-daemon
2012-03-25 17:21 ` bugzilla-daemon
2012-03-27  4:41 ` bugzilla-daemon
2012-03-27  5:02 ` bugzilla-daemon
2012-03-27  5:33 ` bugzilla-daemon
2012-03-27  7:31   ` Christoph Hellwig
2012-03-27  5:58 ` bugzilla-daemon
2012-03-27  6:05 ` bugzilla-daemon
2012-03-27  6:17 ` bugzilla-daemon
2012-03-27  6:21 ` bugzilla-daemon
2012-04-12 11:37 ` bugzilla-daemon
2012-04-12 15:04 ` bugzilla-daemon
2012-04-13  6:48 ` bugzilla-daemon

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=201203241404.q2OE4ZuN024107@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).