From: Christoph Hellwig <hch@infradead.org>
To: Luca DiMaio <luca.dimaio@chainguard.dev>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-xfs@vger.kernel.org, Scott Moser <smoser@chainguard.dev>,
Dimitri Ledkov <dimitri.ledkov@chainguard.dev>
Subject: Re: Reproducible XFS Filesystems Builds for VMs
Date: Tue, 15 Apr 2025 22:34:34 -0700 [thread overview]
Message-ID: <Z_9Bas9rRB4cMibh@infradead.org> (raw)
In-Reply-To: <CAKBQhKWr_pxBT+jXpaitY3gz6wd1WLqyU4JwQoaRhzKWye8UgQ@mail.gmail.com>
On Mon, Apr 14, 2025 at 06:53:35PM +0200, Luca DiMaio wrote:
> This is a huge step ahead, but we still are facing some missing features/bugs:
>
> - we lose the extended attributes of the files
> - we lose the original timestamps of files and directories
>
> I see that the prototype specification does not include anything about
> those, are there plans to
> support xattrs and timestamps?
I don't think anyone has concrete plans to write this. But patches
would be happily accepted.
next prev parent reply other threads:[~2025-04-16 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 14:38 Reproducible XFS Filesystems Builds for VMs Luca DiMaio
2025-04-14 5:39 ` Christoph Hellwig
2025-04-14 16:53 ` Luca DiMaio
2025-04-16 5:34 ` Christoph Hellwig [this message]
2025-04-16 5:55 ` Darrick J. Wong
2025-04-16 14:50 ` Luca DiMaio
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=Z_9Bas9rRB4cMibh@infradead.org \
--to=hch@infradead.org \
--cc=dimitri.ledkov@chainguard.dev \
--cc=linux-xfs@vger.kernel.org \
--cc=luca.dimaio@chainguard.dev \
--cc=smoser@chainguard.dev \
/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