From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
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>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Overly aggressive .gitignore file?
Date: Wed, 5 Jul 2023 10:31:35 +0200 [thread overview]
Message-ID: <98724f26-8a88-8775-d92b-2b7941e96cd8@petrovitsch.priv.at> (raw)
In-Reply-To: <20230704213415.GA21872@1wt.eu>
On 04/07/2023 23:34, Willy Tarreau wrote:
[...]
> I did and for me on this machine I don't have the problem:
>> willy@pcw:~/linux$ git status
> On branch 20230702-nolibc-series1+2_2
> Your branch is up to date with 'origin/20230702-nolibc-series1+2_2'.
>
> nothing to commit, working tree clean
> willy@pcw:~/linux$ echo blah > 2023-new-patch.mbx
Create 10k files instead of only one and you will have the above described
problem (filename completion takes ages because of untracked files not
shown by `git status`).
Kind regards,
Bernd
--
Bernd Petrovitsch Email : bernd@petrovitsch.priv.at
There is NO CLOUD, just other people's computers. - FSFE
LUGA : http://www.luga.at
next prev parent reply other threads:[~2023-07-05 9:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 19:49 Linus Torvalds
2023-07-04 21:15 ` Willy Tarreau
2023-07-04 21:20 ` Linus Torvalds
2023-07-04 21:34 ` Willy Tarreau
2023-07-04 21:44 ` Linus Torvalds
2023-07-04 21:56 ` Willy Tarreau
2023-07-04 22:14 ` Linus Torvalds
2023-07-04 22:27 ` Willy Tarreau
2023-07-05 0:41 ` Theodore Ts'o
2023-07-05 13:51 ` Konstantin Ryabitsev
2023-07-07 18:51 ` Nick Desaulniers
2023-07-07 19:11 ` Linus Torvalds
2023-07-05 8:31 ` Bernd Petrovitsch [this message]
2023-07-05 1:59 ` Masahiro Yamada
2023-07-05 15:34 ` Theodore Ts'o
2023-07-05 16:28 ` Masahiro Yamada
2023-07-05 3:45 ` Nicolas Schier
2023-07-05 5:04 ` Masahiro Yamada
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=98724f26-8a88-8775-d92b-2b7941e96cd8@petrovitsch.priv.at \
--to=bernd@petrovitsch.priv.at \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®