From: Junio C Hamano <gitster@pobox.com>
To: "Peter B." <pb@das-werkstatt.com>
Cc: git@vger.kernel.org
Subject: Re: git support for "xattrs" (extended filesystem attributes)?
Date: Wed, 27 Nov 2024 04:47:59 +0900 [thread overview]
Message-ID: <xmqqr06xwzdc.fsf@gitster.g> (raw)
In-Reply-To: <5b4c09a9-64bb-e672-e604-120563fc1ad6@das-werkstatt.com> (Peter B.'s message of "Tue, 26 Nov 2024 20:40:32 +0100")
"Peter B." <pb@das-werkstatt.com> writes:
> I'm evaluating and testing extended attributes (xattrs) for
> professional archival collection use.
> I couldn't find any proper documentation/information on how (well) git
> supports including xattrs in version control.
Git tracks contents, pathnames where these contents are stored, and
the executable bit. Nothing else. Not even the owner/group of each
contents, or time of creation or the last modification.
I do not think Git is even aware of xattr at all.
next prev parent reply other threads:[~2024-11-26 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 19:40 git support for "xattrs" (extended filesystem attributes)? Peter B.
2024-11-26 19:47 ` Junio C Hamano [this message]
2024-11-26 22:41 ` Jeff King
2024-11-27 0:00 ` Junio C Hamano
2024-11-27 1:29 ` brian m. carlson
2024-11-27 7:59 ` Peter B.
2024-11-27 20:52 ` Peter B.
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=xmqqr06xwzdc.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pb@das-werkstatt.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;
as well as URLs for NNTP newsgroup(s).