[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y9PioQHu2ShZ2veo@smile.fi.intel.com>
Date: Fri, 27 Jan 2023 16:41:37 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
Nathan Chancellor <nathan@...nel.org>,
Nicolas Schier <nicolas@...sle.eu>,
Nick Desaulniers <ndesaulniers@...gle.com>
Subject: Re: [PATCH v3 2/2] kbuild: make W=1 warn files that are tracked but
ignored by git
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@...el.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
Powered by blists - more mailing lists