From: Jari Aalto <jari.aalto@cante.net>
To: git@vger.kernel.org
Subject: [PATCH] Documentation/gitattributes.txt: Add an example box to demonstrate attributes
Date: Fri, 08 Feb 2008 20:28:01 +0200 [thread overview]
Message-ID: <lk5vtia6.fsf@blue.sea.net> (raw)
Demonstrate the meaning of set, unset, set to value, unspecied in a
asciidoc 'listing block'.
---
Documentation/gitattributes.txt | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt
index 35a29fd..cd99a8e 100644
--- a/Documentation/gitattributes.txt
+++ b/Documentation/gitattributes.txt
@@ -52,6 +52,12 @@ Unspecified::
the path has or does not have the attribute, the
attribute for the path is said to be Unspecified.
+----------------------------------------------------------------
+# Examples: set, unset, set to value, unspecified
+
+*.txt attribute -attribute attribute=value !attribute
+----------------------------------------------------------------
+
When more than one glob pattern matches the path, a later line
overrides an earlier line. This overriding is done per
attribute.
--
1.5.3.8
--
Welcome to FOSS revolution: we fix and modify until it shines
reply other threads:[~2008-02-08 18:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=lk5vtia6.fsf@blue.sea.net \
--to=jari.aalto@cante.net \
--cc=git@vger.kernel.org \
/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).