From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Peter B." <pb@das-werkstatt.com>, git@vger.kernel.org
Subject: Re: git support for "xattrs" (extended filesystem attributes)?
Date: Wed, 27 Nov 2024 09:00:32 +0900 [thread overview]
Message-ID: <xmqq4j3twnof.fsf@gitster.g> (raw)
In-Reply-To: <20241126224124.GB77402@coredump.intra.peff.net> (Jeff King's message of "Tue, 26 Nov 2024 17:41:24 -0500")
Jeff King <peff@peff.net> writes:
> There are some third party tools to save the information in a separate
> file within the history and restore it on checkout.
Ah, you're right of course. We are extensible that way.
> I haven't used them
> myself and some of them are quite old, so YMMV:
>
> - https://etckeeper.branchable.com/
>
> - https://github.com/przemoc/metastore
next prev parent reply other threads:[~2024-11-27 0:00 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
2024-11-26 22:41 ` Jeff King
2024-11-27 0:00 ` Junio C Hamano [this message]
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=xmqq4j3twnof.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pb@das-werkstatt.com \
--cc=peff@peff.net \
/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).