summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 39470cf)
raw | patch | inline | side by side (parent: 39470cf)
author | Jason Merrill <jason@redhat.com> | |
Mon, 6 Apr 2009 15:03:36 +0000 (11:03 -0400) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Wed, 8 Apr 2009 04:58:25 +0000 (21:58 -0700) |
Use the term "toplevel of the work tree" in gitattributes.txt and
gitignore.txt to define the limits of the search for those files.
Signed-off-by: Jason Merrill <jason@redhat.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
gitignore.txt to define the limits of the search for those files.
Signed-off-by: Jason Merrill <jason@redhat.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/gitattributes.txt | patch | blob | history | |
Documentation/gitignore.txt | patch | blob | history |
index 37fff208ffb6ce75911ef439ef140550a48b1a18..c4aebc4351a125ceaa92a8021f54a9849c56d03e 100644 (file)
When deciding what attributes are assigned to a path, git
consults `$GIT_DIR/info/attributes` file (which has the highest
precedence), `.gitattributes` file in the same directory as the
-path in question, and its parent directories (the further the
-directory that contains `.gitattributes` is from the path in
-question, the lower its precedence).
+path in question, and its parent directories up to the toplevel of the
+work tree (the further the directory that contains `.gitattributes`
+is from the path in question, the lower its precedence).
If you wish to affect only a single repository (i.e., to assign
attributes to files that are particular to one user's workflow), then
index 59321a2e82b1e141746d94c439452b52b84994ad..7df3cef46f3cc2a0cb0e0d7197b431b01b3af4fd 100644 (file)
* Patterns read from a `.gitignore` file in the same directory
as the path, or in any parent directory, with patterns in the
- higher level files (up to the root) being overridden by those in
- lower level files down to the directory containing the file.
+ higher level files (up to the toplevel of the work tree) being overridden
+ by those in lower level files down to the directory containing the file.
These patterns match relative to the location of the
`.gitignore` file. A project normally includes such
`.gitignore` files in its repository, containing patterns for