From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH v3 2/2] kbuild: make W=1 warn files that are tracked but ignored by git
Date: Fri, 27 Jan 2023 16:41:37 +0200 [thread overview]
Message-ID: <Y9PioQHu2ShZ2veo@smile.fi.intel.com> (raw)
In-Reply-To: <CAK7LNASJ6j7XEZ-poS+Qq+8nZ5iztLTuTSgkr+fMka7HYH8ekQ@mail.gmail.com>
On Fri, Jan 27, 2023 at 11:31:07PM +0900, Masahiro Yamada wrote:
> On Fri, Jan 27, 2023 at 10:25 PM Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> >
> > On Thu, Dec 29, 2022 at 04:43:10PM +0900, Masahiro Yamada wrote:
> > > The top .gitignore comments about how to detect files breaking
> > > .gitignore rules, but people rarely care about it.
> > >
> > > Add a new W=1 warning to detect files that are tracked but ignored by
> > > git. If git is not installed or the source tree is not tracked by git
> > > at all, this script does not print anything.
> > >
> > > Running it on v6.2-rc1 detected the following:
> >
> > Since patch was published there is no sign it was ever meet Linux Next.
> > What's the plan?
>
> Oh?
Sorry, my mistake. I need to understand why these patches do not fix
the issue I have.
> I can see this patch in linux-next.
>
> $ git log next-20230127 -- scripts/misc-check
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-01-27 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 7:43 [PATCH v3 1/2] .gitignore: update the command to check tracked files being ignored Masahiro Yamada
2022-12-29 7:43 ` [PATCH v3 2/2] kbuild: make W=1 warn files that are tracked but ignored by git Masahiro Yamada
2022-12-29 14:23 ` Nicolas Schier
2022-12-30 3:10 ` Masahiro Yamada
2023-01-27 13:25 ` Andy Shevchenko
2023-01-27 14:31 ` Masahiro Yamada
2023-01-27 14:41 ` Andy Shevchenko [this message]
2023-01-27 14:50 ` Andy Shevchenko
2023-01-27 14:52 ` 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=Y9PioQHu2ShZ2veo@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.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