From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/1] perf bench bpf: Add missing .gitignore file
Date: Tue, 23 Jun 2026 21:50:29 -0300 [thread overview]
Message-ID: <ajsp1UEtRk4PY0cW@x1> (raw)
In-Reply-To: <CAHk-=wjntSyV0sZvOU4wAKU83GiBWQ0Y2bbvtg84QSg6SbpgDw@mail.gmail.com>
On Tue, Jun 23, 2026 at 05:42:58PM -0700, Linus Torvalds wrote:
> On Tue, 23 Jun 2026 at 17:32, Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> >
> > .tmp is created as well.
>
> Note that the top-level .gitignore makes sure that we ignore any
> dot-files by default (along with a lot of the usual patterns, of
> course - not just object files, but various other binary file
> endings).
>
> ( Yes, gitignore files do allow overrides to "un-ignore" files too,
> but almost nobody ever uses that, there's seldom any reason for some
> top-level file to say "ignore all generated files of this pattern" and
> then a subdirectory gitignore says "but not this pattern". Some crazy
> directories do say "ignore everything" and then they explicitly
> unignore some patterns, but honestly, that's a mark of a diseased mind
> )
Yeah, but having .tmp there its kinda like not depending on having the
prototype for a function indirectly obtained via some include chain, by
luck, having .tmp there documents that that thing is (or a strong maybe,
in the case of vmlinux.h) generated there and should be ignored.
Anyway, now it is ignored, doubly so in the case of .tmp.
- Arnaldo
prev parent reply other threads:[~2026-06-24 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 0:05 [PATCH 1/1] perf bench bpf: Add missing .gitignore file Arnaldo Carvalho de Melo
2026-06-24 0:27 ` Namhyung Kim
2026-06-24 0:32 ` Arnaldo Carvalho de Melo
2026-06-24 0:42 ` Linus Torvalds
2026-06-24 0:50 ` Arnaldo Carvalho de Melo [this message]
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=ajsp1UEtRk4PY0cW@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=torvalds@linux-foundation.org \
/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