linux-kernel - Re: Overly aggressive .gitignore file?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 4 Jul 2023 14:20:36 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Willy Tarreau <w@....eu>
Cc:     Masahiro Yamada <masahiroy@...nel.org>,
        Nicolas Schier <nicolas@...sle.eu>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Overly aggressive .gitignore file?

On Tue, 4 Jul 2023 at 14:15, Willy Tarreau <w@....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