From: Michael Haggerty <mhagger@alum.mit.edu>
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net,
Michael Haggerty <mhagger@alum.mit.edu>
Subject: [PATCH 1/2] gitattributes: Clarify discussion of attribute macros
Date: Wed, 3 Aug 2011 15:41:29 +0200 [thread overview]
Message-ID: <1312378890-31703-2-git-send-email-mhagger@alum.mit.edu> (raw)
In-Reply-To: <1312378890-31703-1-git-send-email-mhagger@alum.mit.edu>
In particular, make it clear that attribute macros are themselves
recorded as attributes in addition to setting other attributes.
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
---
Documentation/gitattributes.txt | 13 ++++++++-----
1 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt
index 412c55b..ccb3f3f 100644
--- a/Documentation/gitattributes.txt
+++ b/Documentation/gitattributes.txt
@@ -879,16 +879,19 @@ produced for, any binary file you track. You would need to specify e.g.
------------
but that may become cumbersome, when you have many attributes. Using
-attribute macros, you can specify groups of attributes set or unset at
-the same time. The system knows a built-in attribute macro, `binary`:
+attribute macros, you can define an attribute that, when set, also
+sets or unsets a number of other attributes at the same time. The
+system knows a built-in attribute macro, `binary`:
------------
*.jpg binary
------------
-which is equivalent to the above. Note that the attribute macros can only
-be "Set" (see the above example that sets "binary" macro as if it were an
-ordinary attribute --- setting it in turn unsets "text" and "diff").
+Setting the "binary" attribute also unsets the "text" and "diff"
+attributes as above. Note that attribute macros can only be "Set",
+though setting one might have the effect of setting or unsetting other
+attributes or even returning other attributes to the "Unspecified"
+state.
DEFINING ATTRIBUTE MACROS
--
1.7.6.8.gd2879
next prev parent reply other threads:[~2011-08-03 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 13:41 [PATCH 0/2] Clarify semantics of git attribute macros Michael Haggerty
2011-08-03 13:41 ` Michael Haggerty [this message]
2011-08-03 19:46 ` [PATCH 1/2] gitattributes: Clarify discussion of " Jeff King
2011-08-03 21:40 ` Junio C Hamano
2011-08-03 22:40 ` Jeff King
2011-08-03 13:41 ` [PATCH 2/2] gitattributes: Reword "attribute macro" to "macro attribute" Michael Haggerty
2011-08-03 21:34 ` [PATCH 0/2] Clarify semantics of git attribute macros Philip Oakley
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=1312378890-31703-2-git-send-email-mhagger@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).