From: Stefan Beller <sbeller@google.com>
To: gitster@pobox.com, pclouds@gmail.com
Cc: git@vger.kernel.org, Stefan Beller <sbeller@google.com>
Subject: [PATCHv9 1/4] Documentation: fix a typo
Date: Thu, 19 May 2016 16:23:20 -0700 [thread overview]
Message-ID: <20160519232323.12775-2-sbeller@google.com> (raw)
In-Reply-To: <20160519232323.12775-1-sbeller@google.com>
Signed-off-by: Stefan Beller <sbeller@google.com>
---
Documentation/gitattributes.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt
index e3b1de8..af2c682 100644
--- a/Documentation/gitattributes.txt
+++ b/Documentation/gitattributes.txt
@@ -86,7 +86,7 @@ is either not set or empty, $HOME/.config/git/attributes is used instead.
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
+Sometimes you would need to override a setting of an attribute
for a path to `Unspecified` state. This can be done by listing
the name of the attribute prefixed with an exclamation point `!`.
--
2.8.2.123.gb4ad9b6.dirty
next prev parent reply other threads:[~2016-05-19 23:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 23:23 [PATCHv9 0/4] pathspec magic extension to search for attributes Stefan Beller
2016-05-19 23:23 ` Stefan Beller [this message]
2016-05-19 23:23 ` [PATCHv9 2/4] pathspec: move long magic parsing out of prefix_pathspec Stefan Beller
2016-05-19 23:23 ` [PATCHv9 3/4] pathspec: move prefix check out of the inner loop Stefan Beller
2016-05-19 23:23 ` [PATCHv9 4/4] pathspec: allow querying for attributes Stefan Beller
2016-05-19 23:32 ` Junio C Hamano
2016-05-20 18:15 ` Junio C Hamano
2016-05-20 18:21 ` Stefan Beller
2016-05-20 18:31 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160519232323.12775-2-sbeller@google.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).