Documentation: user-manual: "git commit -a" doesn't motivate .gitignore
"git commit -a" ignores untracked files and follows all tracked files, regardless of whether they are listed in .gitignore. So don't use it to motivate gitignore. Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu> Acked-by: J. Bruce Fields <bfields@fieldses.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jonathan Nieder committed
Aug 6, 2008 at 16:22 UTC
7be73ae94e6dac3d1c41268a13b02ff7203c0631
1 file changed
+2
-2
Documentation/user-manual.txt
+2
-2
@@ -1128,8 +1128,8 @@ This typically includes files generated by a build process or temporary
1128
backup files made by your editor. Of course, 'not' tracking files with git
1129
is just a matter of 'not' calling "`git-add`" on them. But it quickly becomes
1130
annoying to have these untracked files lying around; e.g. they make
1131
-"`git add .`" and "`git commit -a`" practically useless, and they keep
1132
-showing up in the output of "`git status`".
1131
+"`git add .`" practically useless, and they keep showing up in the output of
1132
+"`git status`".
1133
1134
You can tell git to ignore certain files by creating a file called .gitignore
1135
in the top level of your working directory, with contents such as: