From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: wangfeng wangfeng <wangfeng.v1.1985@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Can git detect and manage source file's extensional attribute by command 'setfattr' ?
Date: Thu, 4 Sep 2014 13:07:28 +0000 [thread overview]
Message-ID: <20140904130728.GB17505@vauxhall.crustytoothpaste.net> (raw)
In-Reply-To: <CAHbSJRD=S4u=_Ke3UKfzaVdsPnjvkKf0VYBjo8sNjFXM32wKTQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
On Thu, Sep 04, 2014 at 04:11:06PM +0800, wangfeng wangfeng wrote:
> Hi ,
> I know that git can cope with file's chmod. But how about
> setfattr? I have tried to set some extensional attribute with command
> :
> ####
> setfattr -n user.t1 -v 1 testfile.txt
> ####
> It seems like git cannot detect it. So do I need some config option
> for git? Or doesn't it have this feature?
> Thanks very much.
No, Git doesn't support extended attributes natively. In fact, the only
modes that Git stores are the file type and the executable bit.
If you need to store this information, you could either have it
recreated by running, say, a Makefile, or you could see if the filter
functionality of .gitattributes does what you want.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-09-04 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 8:11 Can git detect and manage source file's extensional attribute by command 'setfattr' ? wangfeng wangfeng
2014-09-04 13:07 ` brian m. carlson [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140904130728.GB17505@vauxhall.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=wangfeng.v1.1985@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).