From: Robert Yang <liezhi.yang@windriver.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Zheng Liu <gnehzuil.liu@gmail.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: e2fsprogs: mke2fs -d: copy the Extended Attributes
Date: Fri, 18 Apr 2014 01:37:11 +0800 [thread overview]
Message-ID: <53501147.7040109@windriver.com> (raw)
In-Reply-To: <53501061.9040505@windriver.com>
On 04/18/2014 01:33 AM, Robert Yang wrote:
>
>
> On 04/18/2014 12:27 AM, Theodore Ts'o wrote:
>> On Thu, Apr 17, 2014 at 03:14:34PM +0800, Robert Yang wrote:
>>>
>>> The "mke2fs -d" doesn't copy the file's extended attributes into the
>>> device currently, I'd like to make it work and submit a patch for it
>>> if it is acceptable by e2fsprogs. Maybe we can add a "[-x xattr]"
>>> option for "mke2fs -d" to make it copy the extended attributes.
>>
>> Any reason not to always copy the xattrs if they exist?
Always copy the xattrs if they exist also sounds reasonable, I will try
to investigate more usecases.
// Robert
>>
>> If we want to add a new option for a feature like this which is fairly
>> exotic, my preference would be to either use the -E mechanism and make
>> it be an extended option, or to put it in /etc/mke2fs.conf.
>
> Thanks for the reply, yes, add the new option "[-x xattr]" sounds
> strange, I will try to use the -E mechanism and make it be an
> extended option.
>
> Have a good day, I have to go to sleep now.
>
> // Robert
>
>>
>> Regards,
>>
>> - Ted
>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
prev parent reply other threads:[~2014-04-17 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 7:14 e2fsprogs: mke2fs -d: copy the Extended Attributes Robert Yang
2014-04-17 16:27 ` Theodore Ts'o
2014-04-17 17:33 ` Robert Yang
2014-04-17 17:37 ` Robert Yang [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=53501147.7040109@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=darrick.wong@oracle.com \
--cc=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).