Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CAHk-=wiJHMje8cpiTajqrLrM23wZK0SWetuK1Bd67c0OGM_BzQ@mail.gmail.com>
 <20230704211509.GA21834@1wt.eu>
In-Reply-To: <20230704211509.GA21834@1wt.eu>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue, 4 Jul 2023 14:20:36 -0700
Message-ID: <CAHk-=wjH4O6v_EwVB=t_6Haky2jOiejHbCkCTvgNQWo1ghy8-w@mail.gmail.com>
Subject: Re: Overly aggressive .gitignore file?
To:     Willy Tarreau <w@1wt.eu>
Cc:     Masahiro Yamada <masahiroy@kernel.org>,
        Nicolas Schier <nicolas@fjasle.eu>,
        Nick Desaulniers <ndesaulniers@google.com>,
        Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, 4 Jul 2023 at 14:15, Willy Tarreau <w@1wt.eu> wrote:
>
> I don't understand why your completion on "git am" should rely on
> *tracked* files.

It doesn't.

Read that email again.

It fails on *untracked* files that are hidden from "git status" and
friends by our .gitignore pattern:

   *.mbx

added by commit 534066a983df (".gitignore: ignore *.cover and *.mbx")

So when I have those old stale mbx files around, I don't see them,
because "git status" will happily say

    nothing to commit, working tree clean

with no mention of those old turds.

Really. Try it.

> From a workflow perspective that makes no sense,
> as by definition, git am will consume only *untracked* files.

I don't think you actually read my email.

            Linus