{"thread":{"id":"4862","subject":"[PATCH] documentation about exclude/ignore files","startedAt":"2006-07-12T19:54:51Z","lastAt":"2006-07-13T07:49:22Z","messageCount":3,"participants":["Matthias Lederhofer","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"23724","messageId":"E1G0knL-0007PL-86@moooo.ath.cx","threadId":"4862","inReplyTo":null,"subject":"[PATCH] documentation about exclude/ignore files","fromName":"Matthias Lederhofer","fromEmail":"matled@gmx.net","sentAt":"2006-07-12T19:54:51Z","receivedAt":"2006-07-12T19:54:51Z","isPatch":true,"sender":{"key":"matled@gmx.net","avatar":null},"body":"---\nUse .git/info/exclude in the example in git-ls-files.txt as .gitignore\nis used there and update the list of commands looking at\n.git/info/exclude in repository-layout.txt.\n\n---\n Documentation/git-ls-files.txt      |    4 ++--\n Documentation/repository-layout.txt |    8 +++++---\n 2 files changed, 7 insertions(+), 5 deletions(-)\n\ndiff --git a/Documentation/git-ls-files.txt b/Documentation/git-ls-files.txt\nindex 4d8a2ad..8520b97 100644\n--- a/Documentation/git-ls-files.txt\n+++ b/Documentation/git-ls-files.txt\n@@ -207,7 +207,7 @@ An exclude pattern is of the following f\n An example:\n \n --------------------------------------------------------------\n-    $ cat .git/ignore\n+    $ cat .git/info/exclude\n     # ignore objects and archives, anywhere in the tree.\n     *.[oa]\n     $ cat Documentation/.gitignore\n@@ -217,7 +217,7 @@ An example:\n     !foo.html\n     $ git-ls-files --ignored \\\n         --exclude='Documentation/*.[0-9]' \\\n-        --exclude-from=.git/ignore \\\n+        --exclude-from=.git/info/exclude \\\n         --exclude-per-directory=.gitignore\n --------------------------------------------------------------\n \ndiff --git a/Documentation/repository-layout.txt b/Documentation/repository-layout.txt\nindex b52dfdc..275d18b 100644\n--- a/Documentation/repository-layout.txt\n+++ b/Documentation/repository-layout.txt\n@@ -120,9 +120,11 @@ info/grafts::\n \n info/exclude::\n \tThis file, by convention among Porcelains, stores the\n-\texclude pattern list.  `git status` looks at it, but\n-\totherwise it is not looked at by any of the core git\n-\tcommands.\n+\texclude pattern list. `.gitignore` is the per-directory\n+\tignore file.  `git status`, `git add`, `git rm` and `git\n+\tclean` look at it but the core git commands do not look\n+\tat it.  See also: gitlink:git-ls-files[1] `--exclude-from`\n+\tand `--exclude-per-directory`.\n \n remotes::\n \tStores shorthands to be used to give URL and default\n-- \n1.4.1.gb16f\n"},{"id":"23738","messageId":"7vy7uyw206.fsf@assigned-by-dhcp.cox.net","threadId":"4862","inReplyTo":"E1G0knL-0007PL-86@moooo.ath.cx","subject":"Re: [PATCH] documentation about exclude/ignore files","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-07-13T04:40:57Z","receivedAt":"2006-07-13T04:40:57Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Matthias Lederhofer <matled@gmx.net> writes:\n\n> ---\n> Use .git/info/exclude in the example in git-ls-files.txt as .gitignore\n> is used there and update the list of commands looking at\n> .git/info/exclude in repository-layout.txt.\n>\n> ---\n>  Documentation/git-ls-files.txt      |    4 ++--\n>  Documentation/repository-layout.txt |    8 +++++---\n>  2 files changed, 7 insertions(+), 5 deletions(-)\n\nWhy do you start the message with three dashes that says \"the\nbelow will _not_ go to the commit log message\"?\n\nThe changes look good.  Please sign your patches.\n"},{"id":"23748","messageId":"E1G0vwo-0007IB-46@moooo.ath.cx","threadId":"4862","inReplyTo":"7vy7uyw206.fsf@assigned-by-dhcp.cox.net","subject":"Re: [PATCH] documentation about exclude/ignore files","fromName":"Matthias Lederhofer","fromEmail":"matled@gmx.net","sentAt":"2006-07-13T07:49:22Z","receivedAt":"2006-07-13T07:49:22Z","isPatch":true,"sender":{"key":"matled@gmx.net","avatar":null},"body":"Junio C Hamano <junkio@cox.net> wrote:\n> Why do you start the message with three dashes that says \"the\n> below will _not_ go to the commit log message\"?\nI was not sure if this comment should really go into the commit\nmessage.\n\n> The changes look good.  Please sign your patches.\nArgh, I just keep forgetting this, sorry.\n"}]}