From: Stefan Beller <sbeller@google.com>
To: unlisted-recipients:; (no To-header on input)
Cc: pclouds@gmail.com, gitster@pobox.com, git@vger.kernel.org,
Jens.Lehmann@web.de, jrnieder@gmail.com,
Stefan Beller <sbeller@google.com>
Subject: [PATCH 2/5] Documentation: correct typo in example for querying attributes
Date: Fri, 13 May 2016 16:13:23 -0700 [thread overview]
Message-ID: <20160513231326.8994-3-sbeller@google.com> (raw)
In-Reply-To: <20160513231326.8994-1-sbeller@google.com>
The introductory text of the example has a typo in the
specification which makes it harder to follow that example.
Signed-off-by: Stefan Beller <sbeller@google.com>
---
Documentation/technical/api-gitattributes.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/technical/api-gitattributes.txt b/Documentation/technical/api-gitattributes.txt
index 2602668..36fc9af 100644
--- a/Documentation/technical/api-gitattributes.txt
+++ b/Documentation/technical/api-gitattributes.txt
@@ -61,7 +61,7 @@ Querying Specific Attributes
Example
-------
-To see how attributes "crlf" and "indent" are set for different paths.
+To see how attributes "crlf" and "ident" are set for different paths.
. Prepare an array of `struct git_attr_check` with two elements (because
we are checking two attributes). Initialize their `attr` member with
--
2.8.2.401.g6647087.dirty
next prev parent reply other threads:[~2016-05-13 23:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 23:13 [PATCHv2 0/5] pathspec labels [WAS: submodule groups] Stefan Beller
2016-05-13 23:13 ` [PATCH 1/5] Documentation: fix a typo Stefan Beller
2016-05-13 23:13 ` Stefan Beller [this message]
2016-05-13 23:13 ` [PATCH 3/5] pathspec: move long magic parsing out of prefix_pathspec Stefan Beller
2016-05-13 23:13 ` [PATCH 4/5] pathspec: move prefix check out of the inner loop Stefan Beller
2016-05-13 23:13 ` [PATCH 5/5] pathspec: record labels Stefan Beller
2016-05-14 19:23 ` Junio C Hamano
2016-05-16 17:16 ` Stefan Beller
2016-05-16 17:38 ` Junio C Hamano
2016-05-16 17:46 ` Stefan Beller
2016-05-16 18:52 ` Junio C Hamano
2016-05-16 19:03 ` Stefan Beller
2016-05-16 19:08 ` Junio C Hamano
2016-05-16 19:12 ` Stefan Beller
2016-05-16 19:27 ` Junio C Hamano
2016-05-16 17:55 ` Stefan Beller
2016-05-16 18:43 ` Junio C Hamano
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=20160513231326.8994-3-sbeller@google.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.com \
/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).