Re: Documentation: user-manual: "git commit -a" doesn't motivate .gitignore
On Wed, Aug 06, 2008 at 04:22:00PM -0500, Jonathan Nieder wrote:
> "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.
Show 34 quoted lines
>
> Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu>
> ---
> I noticed this while reading through the git-scm book, which
> looks very good. If I am missing something, I would be very
> happy to know. Maybe the sort of person that wants to track the
> exact contents of the working tree would prefer
> "git commit -a -i ." over "git commit -a"?
>
> Documentation/user-manual.txt | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
> index 43f4e39..f421689 100644
> --- a/Documentation/user-manual.txt
> +++ b/Documentation/user-manual.txt
> @@ -1128,8 +1128,8 @@ This typically includes files generated by a build process or temporary
> backup files made by your editor. Of course, 'not' tracking files with git
> is just a matter of 'not' calling "`git-add`" on them. But it quickly becomes
> annoying to have these untracked files lying around; e.g. they make
> -"`git add .`" and "`git commit -a`" practically useless, and they keep
> -showing up in the output of "`git status`".
> +"`git add .`" practically useless, and they keep showing up in the output of
> +"`git status`".
>
> You can tell git to ignore certain files by creating a file called .gitignore
> in the top level of your working directory, with contents such as:
> --
> 1.6.0.rc1.228.ge730
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html