From: Andreas Schwab <schwab@linux-m68k.org>
To: SLONIK.AZ@gmail.com
Cc: Junio C Hamano <gitster@pobox.com>,
Andy Parkins <andyparkins@gmail.com>,
git@vger.kernel.org
Subject: Re: git-status and git-diff now very slow in project with a submodule
Date: Fri, 21 May 2010 19:54:25 +0200 [thread overview]
Message-ID: <m2tyq1qgxa.fsf@igel.home> (raw)
In-Reply-To: <AANLkTilctjct-a911H14XMnaBydYR1I6lPbEuFThTJ99@mail.gmail.com> (Leo Razoumov's message of "Fri, 21 May 2010 08:52:13 -0400")
Leo Razoumov <slonik.az@gmail.com> writes:
> Speaking of .gitignore and untracked files. Explicitly mentioning all
> such untracked files in .gitignore is often unpractical. For example,
> during build process some large projects autogenerate many temporary
> *.c *.h *.cpp files. Hunting all of them down and adding to
> .gitignore is a waste of time and one cannot use globs *.c *.h for
> obvious reasons.
You can actually, since tracked files are never ignored.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-05-21 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 10:01 git-status and git-diff now very slow in project with a submodule Andy Parkins
2010-05-20 10:10 ` Stefan Naewe
2010-05-20 11:37 ` Andy Parkins
2010-05-20 15:52 ` Michael J Gruber
2010-05-20 17:45 ` Andy Parkins
2010-05-20 17:49 ` Jens Lehmann
2010-05-20 18:01 ` Andy Parkins
2010-05-21 12:36 ` Nguyen Thai Ngoc Duy
2010-05-20 13:28 ` Junio C Hamano
2010-05-20 17:17 ` Andy Parkins
2010-05-20 22:59 ` Junio C Hamano
2010-05-21 12:05 ` Jens Lehmann
2010-05-21 12:52 ` Leo Razoumov
2010-05-21 17:54 ` Andreas Schwab [this message]
2010-05-22 12:05 ` Jens Lehmann
2010-05-22 12:08 ` Jens Lehmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2tyq1qgxa.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=SLONIK.AZ@gmail.com \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.