From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>,
Danny Milosavljevic <dannym@scratchpost.org>,
Samuel Thibault <samuel.thibault@gnu.org>
Subject: Re: [PATCH v2] ext4: support xattr gnu.* namespace for the Hurd
Date: Fri, 29 May 2020 10:39:39 +0200 [thread overview]
Message-ID: <87imgfuoc4.fsf@gnu.org> (raw)
In-Reply-To: <20200529032505.GM228632@mit.edu> (Theodore Y. Ts'o's message of "Thu, 28 May 2020 23:25:05 -0400")
Theodore Y. Ts'o writes:
Hello!
> On Mon, May 25, 2020 at 09:39:40PM +0200, Jan (janneke) Nieuwenhuizen wrote:
>> The Hurd gained[0] support for moving the translator and author
>> fields out of the inode and into the "gnu.*" xattr namespace.
>>
>> In anticipation of that, an xattr INDEX was reserved[1]. The Hurd has
>> now been brought into compliance[2] with that.
>>
>> This patch adds support for reading and writing such attributes from
>> Linux; you can now do something like
[...]
>
> This patch is missing a Signed-off-by. If you don't understand why
> this is really important, please read:
>
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
Ah, that makes sense. Sorry for omitting that/being not clear on it.
> Can you resubmit with the DCO or confirm that it's OK for me to add
> your Signed-off-by?
Yes, that's OK, please do! I am the original author of this patch.
Greetings,
Janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2020-05-29 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 19:39 [PATCH v2] ext4: support xattr gnu.* namespace for the Hurd Jan (janneke) Nieuwenhuizen
2020-05-29 3:25 ` Theodore Y. Ts'o
2020-05-29 8:39 ` Jan Nieuwenhuizen [this message]
2020-06-12 17:38 ` Theodore Y. Ts'o
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=87imgfuoc4.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=adilger.kernel@dilger.ca \
--cc=dannym@scratchpost.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@gnu.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).