{"thread":{"id":"50668","subject":"[PATCH 0/1] update git-clean.txt","startedAt":"2019-03-06T10:42:23Z","lastAt":"2019-03-08T00:18:00Z","messageCount":13,"participants":["Denton Liu","Martin Ågren","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":1},"messages":[{"id":"370804","messageId":"cover.1551868745.git.liu.denton@gmail.com","threadId":"50668","inReplyTo":null,"subject":"[PATCH 0/1] update git-clean.txt","fromName":"Denton Liu","fromEmail":"liu.denton@gmail.com","sentAt":"2019-03-06T10:42:19Z","receivedAt":"2019-03-06T10:42:23Z","isPatch":true,"sender":{"key":"liu.denton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9620836?v=4"},"body":"Robert reported that core.excludesFile was not mentioned in the\ngit-clean docs[1]. This cleans that up by mentioning that in the docs.\n\n[1]: https://public-inbox.org/git/alpine.LFD.2.21.1902231328560.2222@localhost.localdomain/\n\nDenton Liu (1):\n git-clean.txt: specify core.excludesFile variable is used\n\n Documentation/git-clean.txt | 8 +++++---\n 1 file changed, 5 insertions(+), 3 deletions(-)\n\n-- \n2.21.0.317.g7f43cb445c\n\n"},{"id":"370805","messageId":"f8bc322cc5727d9cf45037f4231f88956f07b7f3.1551868745.git.liu.denton@gmail.com","threadId":"50668","inReplyTo":"cover.1551868745.git.liu.denton@gmail.com","subject":"[PATCH 1/1] git-clean.txt: specify core.excludesFile variable is used","fromName":"Denton Liu","fromEmail":"liu.denton@gmail.com","sentAt":"2019-03-06T10:42:22Z","receivedAt":"2019-03-06T10:42:26Z","isPatch":true,"sender":{"key":"liu.denton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9620836?v=4"},"body":"In the git-clean documentation, -x and -e documented .gitignore,\n$GIT_DIR/info/excludes but neglected to mention the file pointed to by\ncore.excludesFile.\n\nExplicitly mention that variable so that the list is exhaustive.\n\nReported-by: Robert P. J. Day \nSigned-off-by: Denton Liu \n---\n Documentation/git-clean.txt | 8 +++++---\n 1 file changed, 5 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git-clean.txt b/Documentation/git-clean.txt\nindex 03056dad0d..c6023b742c 100644\n--- a/Documentation/git-clean.txt\n+++ b/Documentation/git-clean.txt\n@@ -55,13 +55,15 @@ OPTIONS\n \n -e ::\n --exclude=::\n-\tIn addition to those found in .gitignore (per directory) and\n-\t$GIT_DIR/info/exclude, also consider these patterns to be in the\n+\tIn addition to those found in .gitignore (per directory),\n+\t$GIT_DIR/info/exclude, and the `core.excludesFile` variable, also\n+\tconsider these patterns to be in the\n \tset of the ignore rules in effect.\n \n -x::\n \tDon't use the standard ignore rules read from .gitignore (per\n-\tdirectory) and $GIT_DIR/info/exclude, but do still use the ignore\n+\tdirectory), $GIT_DIR/info/exclude, and the `core.excludesFile`\n+\tvariable, but do still use the ignore\n \trules given with `-e` options. This allows removing all untracked\n \tfiles, including build products. This can be used (possibly in\n \tconjunction with 'git reset') to create a pristine\n-- \n2.21.0.317.g7f43cb445c\n\n"},{"id":"370827","messageId":"CAN0heSqTCQaTgWq4+-dxP0DFjtL=syq_W=T0cb66-2YPB4Tc-w@mail.gmail.com","threadId":"50668","inReplyTo":"f8bc322cc5727d9cf45037f4231f88956f07b7f3.1551868745.git.liu.denton@gmail.com","subject":"Re: [PATCH 1/1] git-clean.txt: specify core.excludesFile variable is used","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2019-03-06T20:22:01Z","receivedAt":"2019-03-06T20:22:16Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"On Wed, 6 Mar 2019 at 12:17, Denton Liu wrote:\n>\n> In the git-clean documentation, -x and -e documented .gitignore,\n> $GIT_DIR/info/excludes but neglected to mention the file pointed to by\n> core.excludesFile.\n\nNit: I suppose it doesn't so much document it, as mention it. So\n\n In the git-clean documentation, we mention .gitignore and\n $GIT_DIR/info/excludes, but neglect to mention the file pointed to by\n core.excludesFile.\n\nperhaps.\n\n> Explicitly mention that variable so that the list is exhaustive.\n\n> -e ::\n> --exclude=::\n> - In addition to those found in .gitignore (per directory) and\n> - $GIT_DIR/info/exclude, also consider these patterns to be in the\n> + In addition to those found in .gitignore (per directory),\n> + $GIT_DIR/info/exclude, and the `core.excludesFile` variable, also\n> + consider these patterns to be in the\n> set of the ignore rules in effect.\n\nThe commit message correctly phrases it as \"the file pointed to by\",\nwhereas this could give the impression that the config variable is\nsupposed to provide patterns, not a filename. But if the choice is\nbetween creating a longer, more language-lawyer-correct phrasing and a\nshorter one that everyone will understand, I'll choose the latter any\nday.\n\nBut on the topic of preferring shorter, I sort of wonder if we really\nneed to provide all of those filenames here. The point we're trying to\nmake is that we consider another source. So something like this would be\njust as technically correct, I think:\n\n Use the given exclude pattern in addition to those found in .gitignore\n and similar files (see linkgit:gitignore[5]).\n\nThis also places the interesting (IMHO) part of the sentence at the\nfront, rather than at the end.\n\nFrom gitignore(5), I get the impression that patterns provided using\n`--exclude` take precedence over those found in those files we're\nlisting. Whether or not that is the case here might perhaps be more\ninteresting than the exact list of files. Does that make sense?\n\n> -x::\n> Don't use the standard ignore rules read from .gitignore (per\n> - directory) and $GIT_DIR/info/exclude, but do still use the ignore\n> + directory), $GIT_DIR/info/exclude, and the `core.excludesFile`\n> + variable, but do still use the ignore\n> rules given with `-e` options. This allows removing all untracked\n> files, including build products. This can be used (possibly in\n> conjunction with 'git reset') to create a pristine\n\nNit: Not new in this patch, but I think you could add a few `backticks`\nwhile you're here to render things like `.gitignore` and\n`$GIT_DIR/info/exclude/` in monospace.\n\nMartin\n"},{"id":"370852","messageId":"xmqqmum7o6wz.fsf@gitster-ct.c.googlers.com","threadId":"50668","inReplyTo":"CAN0heSqTCQaTgWq4+-dxP0DFjtL=syq_W=T0cb66-2YPB4Tc-w@mail.gmail.com","subject":"Re: [PATCH 1/1] git-clean.txt: specify core.excludesFile variable is used","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2019-03-07T00:38:20Z","receivedAt":"2019-03-07T00:38:25Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Martin Ågren writes:\n\n> But on the topic of preferring shorter, I sort of wonder if we really\n> need to provide all of those filenames here. The point we're trying to\n> make is that we consider another source. So something like this would be\n> just as technically correct, I think:\n>\n> Use the given exclude pattern in addition to those found in .gitignore\n> and similar files (see linkgit:gitignore[5]).\n\nYes. Unless we devise some mechanism to prevent these text that\nlist the places exclusion list are read from spread across the\ndocumentation set, saying \"found in usual places (see $there)\" and\nmaking sure we have the authoritative single place up-to-date is a\ngood approach.\n"},{"id":"370865","messageId":"cover.1551938421.git.liu.denton@gmail.com","threadId":"50668","inReplyTo":"cover.1551868745.git.liu.denton@gmail.com","subject":"[PATCH v2 0/1] make git-clean.txt more precise","fromName":"Denton Liu","fromEmail":"liu.denton@gmail.com","sentAt":"2019-03-07T06:04:58Z","receivedAt":"2019-03-07T06:05:03Z","isPatch":true,"sender":{"key":"liu.denton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9620836?v=4"},"body":"Robert reported that core.excludesFile was not mentioned in the\ngit-clean docs[1]. This cleans that up by mentioning that in the docs.\n\n[1]: https://public-inbox.org/git/alpine.LFD.2.21.1902231328560.2222@localhost.localdomain/\n\nChanges since v1:\n\n* Use Martin's suggestions of referencing the gitignore(5) instead of\n writing an exhaustive list. Also, sprinkle in some backticks ;)\n\nDenton Liu (1):\n git-clean.txt: clarify ignore pattern files\n\n Documentation/git-clean.txt | 9 ++++-----\n 1 file changed, 4 insertions(+), 5 deletions(-)\n\n-- \n2.21.0.368.gbf248417d7\n\n"},{"id":"370866","messageId":"2eda83517ebad39e14dca9d86b9dc2e0d32e37ef.1551938421.git.liu.denton@gmail.com","threadId":"50668","inReplyTo":"cover.1551938421.git.liu.denton@gmail.com","subject":"[PATCH v2 1/1] git-clean.txt: clarify ignore pattern files","fromName":"Denton Liu","fromEmail":"liu.denton@gmail.com","sentAt":"2019-03-07T06:05:01Z","receivedAt":"2019-03-07T06:05:05Z","isPatch":true,"sender":{"key":"liu.denton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9620836?v=4"},"body":"In the git-clean documentation, -x and -e documented .gitignore,\n$GIT_DIR/info/excludes but neglected to mention the file pointed to by\ncore.excludesFile.\n\nRemove specific list of files and, instead, reference gitignore(5)\ndocumentation so that information is consolidated and the git-clean\ndocumentation is more precise.\n\nReported-by: Robert P. J. Day \nHelped-by: Martin Ågren \nSigned-off-by: Denton Liu \n---\n Documentation/git-clean.txt | 9 ++++-----\n 1 file changed, 4 insertions(+), 5 deletions(-)\n\ndiff --git a/Documentation/git-clean.txt b/Documentation/git-clean.txt\nindex 03056dad0d..d251ef9dd2 100644\n--- a/Documentation/git-clean.txt\n+++ b/Documentation/git-clean.txt\n@@ -55,13 +55,12 @@ OPTIONS\n \n -e ::\n --exclude=::\n-\tIn addition to those found in .gitignore (per directory) and\n-\t$GIT_DIR/info/exclude, also consider these patterns to be in the\n-\tset of the ignore rules in effect.\n+\tUse the exclude pattern in addition to those found in\n+\t`.gitignore` and similar files (see linkgit:gitignore[5]).\n \n -x::\n-\tDon't use the standard ignore rules read from .gitignore (per\n-\tdirectory) and $GIT_DIR/info/exclude, but do still use the ignore\n+\tDon't use the standard ignore rules read from `.gitignore` and\n+\tsimilar files (see linkgit:gitignore[5]), but do still use the ignore\n \trules given with `-e` options. This allows removing all untracked\n \tfiles, including build products. This can be used (possibly in\n \tconjunction with 'git reset') to create a pristine\n-- \n2.21.0.368.gbf248417d7\n\n"},{"id":"370871","messageId":"xmqqlg1rmati.fsf@gitster-ct.c.googlers.com","threadId":"50668","inReplyTo":"2eda83517ebad39e14dca9d86b9dc2e0d32e37ef.1551938421.git.liu.denton@gmail.com","subject":"Re: [PATCH v2 1/1] git-clean.txt: clarify ignore pattern files","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2019-03-07T06:56:57Z","receivedAt":"2019-03-07T06:57:03Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Denton Liu writes:\n\n> -e ::\n> --exclude=::\n> -\tIn addition to those found in .gitignore (per directory) and\n> -\t$GIT_DIR/info/exclude, also consider these patterns to be in the\n> -\tset of the ignore rules in effect.\n> +\tUse the exclude pattern in addition to those found in\n> +\t`.gitignore` and similar files (see linkgit:gitignore[5]).\n> \n> -x::\n> -\tDon't use the standard ignore rules read from .gitignore (per\n> -\tdirectory) and $GIT_DIR/info/exclude, but do still use the ignore\n> +\tDon't use the standard ignore rules read from `.gitignore` and\n> +\tsimilar files (see linkgit:gitignore[5]), but do still use the ignore\n> \trules given with `-e` options. This allows removing all untracked\n> \tfiles, including build products. This can be used (possibly in\n> \tconjunction with 'git reset') to create a pristine\n\nI do agree with the direction to abandon the attempt to be\nexhaustive, which has failed us and will fail. I am not sure if\n\".gitignore and similar files\" is a good phrasing, though.\n\n Don't use the standard ignored rules (see linkgit:gitignore[5]),\n but use the ignore rules given with `-e` options from the\n command line.\n\nperhaps? I dunno.\n\nA related tangent.\n\n\"git add --help\" also has this bit.\n\n CONFIGURATION\n -------------\n\n The optional configuration variable `core.excludesFile` indicates a path to a\n file containing patterns of file names to exclude from git-add, similar to\n $GIT_DIR/info/exclude. Patterns in the exclude file are used in addition to\n those in info/exclude. See linkgit:gitignore[5].\n\nI do not think the omission of per-directory .gitignore from this\ndescription is because the description predates the feature (which\nis the reason why \"git clean\" doc does not mention, by the way), but\nthis probably needs a simliar treatment.\n\nOr perhaps this configuration section should just be removed (or\nmoved to gitignore(5)), as it is not specific to \"git add\".\n"},{"id":"370873","messageId":"CAN0heSrGT1SBt=w8j8G0nnWXDOrn+VYFuk2iPWH9uk22fqzFKw@mail.gmail.com","threadId":"50668","inReplyTo":"xmqqlg1rmati.fsf@gitster-ct.c.googlers.com","subject":"Re: [PATCH v2 1/1] git-clean.txt: clarify ignore pattern files","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2019-03-07T07:37:44Z","receivedAt":"2019-03-07T07:37:59Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"On Thu, 7 Mar 2019 at 07:57, Junio C Hamano wrote:\n>\n> Denton Liu writes:\n>\n> > + Use the exclude pattern in addition to those found in\n> > + `.gitignore` and similar files (see linkgit:gitignore[5]).\n\n> I do agree with the direction to abandon the attempt to be\n> exhaustive, which has failed us and will fail. I am not sure if\n> \".gitignore and similar files\" is a good phrasing, though.\n>\n> Don't use the standard ignored rules (see linkgit:gitignore[5]),\n> but use the ignore rules given with `-e` options from the\n> command line.\n>\n> perhaps? I dunno.\n\nYeah, I like \"the standard ignore rules\" more than my original\nsuggestion. Hmm, I now see you wrote \"the standard ignore/D/ rules\" -- I\nbelieve that's a typo.\n\nMartin\n"},{"id":"370877","messageId":"xmqq1s3jm7c4.fsf@gitster-ct.c.googlers.com","threadId":"50668","inReplyTo":"CAN0heSrGT1SBt=w8j8G0nnWXDOrn+VYFuk2iPWH9uk22fqzFKw@mail.gmail.com","subject":"Re: [PATCH v2 1/1] git-clean.txt: clarify ignore pattern files","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2019-03-07T08:12:11Z","receivedAt":"2019-03-07T08:12:17Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Martin Ågren writes:\n\n> suggestion. Hmm, I now see you wrote \"the standard ignore/D/ rules\" -- I\n> believe that's a typo.\n\nThanks for spotting. Yup, that is a typo.\n"},{"id":"370878","messageId":"cover.1551947030.git.liu.denton@gmail.com","threadId":"50668","inReplyTo":"cover.1551938421.git.liu.denton@gmail.com","subject":"[PATCH v3 0/2] consolidate core.excludesFile docs","fromName":"Denton Liu","fromEmail":"liu.denton@gmail.com","sentAt":"2019-03-07T08:25:25Z","receivedAt":"2019-03-07T08:25:30Z","isPatch":true,"sender":{"key":"liu.denton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9620836?v=4"},"body":"Robert reported that core.excludesFile was not mentioned in the\ngit-clean docs[1]. This cleans that up by mentioning that in the docs.\n\n[1]: https://public-inbox.org/git/alpine.LFD.2.21.1902231328560.2222@localhost.localdomain/\n\nChanges since v1:\n\n* Use Martin's suggestions of referencing the gitignore(5) instead of\n writing an exhaustive list. Also, sprinkle in some backticks ;)\n\nChanges since v2:\n\n* Use Junio's suggestion for rephrasing the text in git-clean.txt\n\n* Move core.excludesFile specific documentation out of git-add.txt and into\n gitignore.txt\n\n\nDenton Liu (2):\n git-clean.txt: clarify ignore pattern files\n Docs: move core.excludesFile from git-add to gitignore\n\n Documentation/git-add.txt | 9 ---------\n Documentation/git-clean.txt | 11 +++++------\n Documentation/gitignore.txt | 8 ++++++++\n 3 files changed, 13 insertions(+), 15 deletions(-)\n\n-- \n2.21.0.368.gbf248417d7\n\n"},{"id":"370879","messageId":"f1bc7d5eb1ad15427f6d14c19c90595d09acabe5.1551947030.git.liu.denton@gmail.com","threadId":"50668","inReplyTo":"cover.1551947030.git.liu.denton@gmail.com","subject":"[PATCH v3 2/2] Docs: move core.excludesFile from git-add to gitignore","fromName":"Denton Liu","fromEmail":"liu.denton@gmail.com","sentAt":"2019-03-07T08:25:30Z","receivedAt":"2019-03-07T08:25:36Z","isPatch":true,"sender":{"key":"liu.denton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9620836?v=4"},"body":"There was a section on configuration mentioning core.excludesFile in\ngit-add.txt. However, the core.excludesFile config variable is not\nexclusive to git-add. Move this description to gitignore.txt to be more\ngeneric.\n---\n Documentation/git-add.txt | 9 ---------\n Documentation/gitignore.txt | 8 ++++++++\n 2 files changed, 8 insertions(+), 9 deletions(-)\n\ndiff --git a/Documentation/git-add.txt b/Documentation/git-add.txt\nindex 37bcab94d5..8b0e4c7fa8 100644\n--- a/Documentation/git-add.txt\n+++ b/Documentation/git-add.txt\n@@ -193,15 +193,6 @@ for \"git add --no-all ...\", i.e. ignored removed files.\n \tfor command-line options).\n \n \n-CONFIGURATION\n--------------\n-\n-The optional configuration variable `core.excludesFile` indicates a path to a\n-file containing patterns of file names to exclude from git-add, similar to\n-$GIT_DIR/info/exclude. Patterns in the exclude file are used in addition to\n-those in info/exclude. See linkgit:gitignore[5].\n-\n-\n EXAMPLES\n --------\n \ndiff --git a/Documentation/gitignore.txt b/Documentation/gitignore.txt\nindex 1c94f08ff4..b5bc9dbff0 100644\n--- a/Documentation/gitignore.txt\n+++ b/Documentation/gitignore.txt\n@@ -132,6 +132,14 @@ full pathname may have special meaning:\n - Other consecutive asterisks are considered regular asterisks and\n will match according to the previous rules.\n \n+CONFIGURATION\n+-------------\n+\n+The optional configuration variable `core.excludesFile` indicates a path to a\n+file containing patterns of file names to exclude, similar to\n+`$GIT_DIR/info/exclude`. Patterns in the exclude file are used in addition to\n+those in `$GIT_DIR/info/exclude`.\n+\n NOTES\n -----\n \n-- \n2.21.0.368.gbf248417d7\n\n"},{"id":"370880","messageId":"caf7156412dc5bef0d12476cf4ef59d9cfee6a54.1551947030.git.liu.denton@gmail.com","threadId":"50668","inReplyTo":"cover.1551947030.git.liu.denton@gmail.com","subject":"[PATCH v3 1/2] git-clean.txt: clarify ignore pattern files","fromName":"Denton Liu","fromEmail":"liu.denton@gmail.com","sentAt":"2019-03-07T08:25:28Z","receivedAt":"2019-03-07T08:25:38Z","isPatch":true,"sender":{"key":"liu.denton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9620836?v=4"},"body":"In the git-clean documentation, -x and -e documented .gitignore,\n$GIT_DIR/info/excludes but neglected to mention the file pointed to by\ncore.excludesFile.\n\nRemove specific list of files and, instead, reference gitignore(5)\ndocumentation so that information is consolidated and the git-clean\ndocumentation is more precise.\n\nReported-by: Robert P. J. Day \nHelped-by: Martin Ågren \nHelped-by: Junio C Hamano \nSigned-off-by: Denton Liu \n---\n Documentation/git-clean.txt | 11 +++++------\n 1 file changed, 5 insertions(+), 6 deletions(-)\n\ndiff --git a/Documentation/git-clean.txt b/Documentation/git-clean.txt\nindex 03056dad0d..db876f7dde 100644\n--- a/Documentation/git-clean.txt\n+++ b/Documentation/git-clean.txt\n@@ -55,14 +55,13 @@ OPTIONS\n \n -e ::\n --exclude=::\n-\tIn addition to those found in .gitignore (per directory) and\n-\t$GIT_DIR/info/exclude, also consider these patterns to be in the\n-\tset of the ignore rules in effect.\n+\tUse the given exclude pattern in addition to the standard ignore rules\n+\t(see linkgit:gitignore[5]).\n \n -x::\n-\tDon't use the standard ignore rules read from .gitignore (per\n-\tdirectory) and $GIT_DIR/info/exclude, but do still use the ignore\n-\trules given with `-e` options. This allows removing all untracked\n+\tDon't use the standard ignore rules (see linkgit:gitignore[5]), but\n+\tstill use the ignore rules given with `-e` options from the command\n+\tline. This allows removing all untracked\n \tfiles, including build products. This can be used (possibly in\n \tconjunction with 'git reset') to create a pristine\n \tworking directory to test a clean build.\n-- \n2.21.0.368.gbf248417d7\n\n"},{"id":"370933","messageId":"xmqqk1hakymk.fsf@gitster-ct.c.googlers.com","threadId":"50668","inReplyTo":"f1bc7d5eb1ad15427f6d14c19c90595d09acabe5.1551947030.git.liu.denton@gmail.com","subject":"Re: [PATCH v3 2/2] Docs: move core.excludesFile from git-add to gitignore","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2019-03-08T00:17:55Z","receivedAt":"2019-03-08T00:18:00Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Denton Liu writes:\n\n> There was a section on configuration mentioning core.excludesFile in\n> git-add.txt. However, the core.excludesFile config variable is not\n> exclusive to git-add. Move this description to gitignore.txt to be more\n> generic.\n> ---\n\nI'll forge your sign-off and queue it like so. Thanks.\n\n-- >8 --\nFrom: Denton Liu \nDate: Thu, 7 Mar 2019 00:25:30 -0800\nSubject: [PATCH] docs: move core.excludesFile from git-add to gitignore\n\nA section in \"git add\" documentation mentions core.excludesFile and\nexplains how it works, but this is not specific to the command.\n\nMove this description to gitignore.txt to be more generic.\n\nSigned-off-by: Denton Liu \nSigned-off-by: Junio C Hamano \n---\n Documentation/git-add.txt | 9 ---------\n Documentation/gitignore.txt | 8 ++++++++\n 2 files changed, 8 insertions(+), 9 deletions(-)\n"}]}