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 0/2] Clarify semantics of git attribute macros
Date: Wed, 3 Aug 2011 15:41:28 +0200 [thread overview]
Message-ID: <1312378890-31703-1-git-send-email-mhagger@alum.mit.edu> (raw)
Make it clearer that attribute macros do not only affect other
attributes, but are attributes themselves.
The second patch changes the nomenclature in gitattributes(5) from
"attribute macro" to "macro attribute", which I think makes the point
a tiny bit clearer. But it is definitely optional.
Michael Haggerty (2):
gitattributes: Clarify discussion of attribute macros
gitattributes: Reword "attribute macro" to "macro attribute"
Documentation/gitattributes.txt | 25 ++++++++++++++-----------
1 files changed, 14 insertions(+), 11 deletions(-)
--
1.7.6.8.gd2879
next 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 Michael Haggerty [this message]
2011-08-03 13:41 ` [PATCH 1/2] gitattributes: Clarify discussion of attribute macros Michael Haggerty
2011-08-03 19:46 ` 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-1-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).