git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/2] gitattributes: Reword "attribute macro" to "macro attribute"

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Aug 3, 2011, 13:41 UTC
Message-ID
<1312378890-31703-3-git-send-email-mhagger@alum.mit.edu>
In-Reply-To
<1312378890-31703-1-git-send-email-mhagger@alum.mit.edu>

The new wording makes it clearer that such a beast is an attribute in addition to being a macro (as opposed to being only a macro that is used for attributes).

Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
---
 Documentation/gitattributes.txt |   18 +++++++++---------
 1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt
index ccb3f3f..2bbe76b 100644
--- a/Documentation/gitattributes.txt
+++ b/Documentation/gitattributes.txt
@@ -79,7 +79,7 @@ Attributes for all users on a system should be placed in the
 `$(prefix)/etc/gitattributes` file.
 
 Sometimes you would need to override an setting of an attribute
-for a path to `unspecified` state.  This can be done by listing
+for a path to `Unspecified` state.  This can be done by listing
 the name of the attribute prefixed with an exclamation point `!`.
 
 
@@ -868,7 +868,7 @@ If this attribute is not set or has an invalid value, the value of the
 (See linkgit:git-config[1]).
 
 
-USING ATTRIBUTE MACROS
+USING MACRO ATTRIBUTES
 ----------------------
 
 You do not want any end-of-line conversions applied to, nor textual diffs
@@ -879,27 +879,27 @@ 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 define an attribute that, when set, also
+macro attributes, 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`:
+system knows a built-in macro attribute, `binary`:
 
 ------------
 *.jpg binary
 ------------
 
 Setting the "binary" attribute also unsets the "text" and "diff"
-attributes as above.  Note that attribute macros can only be "Set",
+attributes as above.  Note that macro attributes 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
+DEFINING MACRO ATTRIBUTES
 -------------------------
 
-Custom attribute macros can be defined only in the `.gitattributes` file
-at the toplevel (i.e. not in any subdirectory).  The built-in attribute
-macro "binary" is equivalent to:
+Custom macro attributes can be defined only in the `.gitattributes`
+file at the toplevel (i.e. not in any subdirectory).  The built-in
+macro attribute "binary" is equivalent to:
 
 ------------
 [attr]binary -diff -text
-- 
1.7.6.8.gd2879
Previous: Jeff KingNext: Philip Oakley
Message 6 of 7 in “Clarify semantics of git attribute macros”
  1. 0/2 Clarify semantics of git attribute macrosMichael Haggerty, Aug 3, 2011
  2. 1/2 gitattributes: Clarify discussion of attribute macrosMichael Haggerty, Aug 3, 2011
  3. Jeff KingAug 3, 2011
  4. Junio C HamanoAug 3, 2011
  5. Jeff KingAug 3, 2011
  6. 2/2 gitattributes: Reword "attribute macro" to "macro attribute"Michael Haggerty, Aug 3, 2011
  7. Philip OakleyAug 3, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.