From: Michael Haggerty <mhagger@alum.mit.edu>
Date: Tue, 26 Jul 2011 12:10:11 GMT
Subject: "git check-attr" lists macros as being "set" -- feature or bug?
Message-ID: <4E2EAEA3.8000307@alum.mit.edu>

I am doing some work on git-check-attr, and I noticed something funny:
If a macro is used to set or clear attributes on a file in
.gitattributes, then the name of the macro itself is listed as an
attribute on that file.  Example:

$ git init
Initialized empty Git repository in /tmp/foo/.git/
$ echo '[attr]notest !test' > .gitattributes
$ echo 'no notest' >> .gitattributes

# This is expected:
$ git check-attr test -- no
no: test: unspecified

# This I found surprising:
$ git check-attr notest -- no
no: notest: set

I don't see the correct behavior documented anywhere.  If this is
considered a bug, then I offer to fix it.  If it is considered a
feature, then I offer to document it.

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/