git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-status and git-diff now very slow in project with a submodule

From
Jens Lehmann <jens.lehmann@web.de>
Date
May 22, 2010, 12:05 UTC
Message-ID
<4BF7C87F.3060207@web.de>
In-Reply-To
<m2tyq1qgxa.fsf@igel.home>
Am 21.05.2010 19:54, schrieb Andreas Schwab:
Show 10 quoted lines
> 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.

Hm, but that would mean newly added files would never show up again (the same .gitignore is used by the developers of that submodule when they do work on it). So I wouldn't add *.c to .gitignore either ...

But I don't consider it a "waste of time" to get the .gitignore straight for pretty much the same reasons I want to see no warnings during compilation: So i can instantly see when something fishy might be going on. I consider that a "best practice" instead.

And for those projects where you can't or don't want to change the .gitignore: Just ignore when "git status" tells you a submodule has "untracked content" (it shows that information since 9297f7).

Previous: Andreas SchwabNext: Jens Lehmann
Message 15 of 16 in “git-status and git-diff now very slow in project with a submodule”
  1. Andy ParkinsMay 20, 2010
  2. Stefan NaeweMay 20, 2010
  3. Andy ParkinsMay 20, 2010
  4. Michael J GruberMay 20, 2010
  5. Andy ParkinsMay 20, 2010
  6. Jens LehmannMay 20, 2010
  7. Andy ParkinsMay 20, 2010
  8. Nguyen Thai Ngoc DuyMay 21, 2010
  9. Junio C HamanoMay 20, 2010
  10. Andy ParkinsMay 20, 2010
  11. Junio C HamanoMay 20, 2010
  12. Jens LehmannMay 21, 2010
  13. Leo RazoumovMay 21, 2010
  14. Andreas SchwabMay 21, 2010
  15. Jens LehmannMay 22, 2010
  16. Jens LehmannMay 22, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.