Re: Overly aggressive .gitignore file?

[Willy Tarreau]

On Tue, Jul 04, 2023 at 03:14:11PM -0700, Linus Torvalds wrote:
> But what do you think "git status" is supposed to do?
> 
> Here's a theory - it's supposed to tell me about the status of my git tree.

I agree with this and use it for the same purpose.

> Maybe it's supposed to tell me about extra files that maybe I should
> be aware of. Maybe I should delete them. Maybe I should commit them.
> Who knows?

Sure but apparently the point of that commit was precisely to avoid
*risking* to commit them for other users, or maybe just not seeing
too many of them when running git status to make sure the rest that
they consider more important is actually committed.

> And  *if* we pretend for a moment that this is what "git status" is
> supposed to do, then maybe it should have reminded me about stale
> random files in that directory that ACTIVELY BREAK MY WORKFLOW.

I agree with this.

> Maybe that isn't your workflow.
> 
> Maybe you're perfectly fine not getting a unique auto-complete,
> because you *want* your git directory filled with irrelevant crap.

It's not a matter of being fine or not fine, it's the way your question
was posed. I'm sorry, but I'm seeing so many times completion do nothing
on some distros when passing certain args to various everyday commands
(to the point that I learned to type "complete -r" to kill stupid rules),
that *my* understanding of "doesn't autocomplete" means exactly that. If
you say "it proposes me the whole list of old turds" I perfectly
understand how annoying that can be, exactly like when I leave plenty of
git-format-patch files and I want to git-am another one and can't spot
it. It's just that *for me* it's not the problem that was presented,
hence my suggestions about completion rules being faulty.

I understand that you might be angry due to a commit that broke your
workflow and that pisses you off, and that maybe your initial message
was written in a hurry to flush your anger, but please also accept
that not everyone possibly understood it the way you hoped it would
be, because it *was* ambiguous.

Anyway, you fixed it so now the problem is solved.

Willy