From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Li Zhijian" <lizhijian@fujitsu.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Tamir Duberstein" <tamird@gmail.com>,
"Vegard Nossum" <vegard.nossum@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/4] .gitignore: ignore Python compiled bytecode
Date: Sat, 19 Apr 2025 19:14:02 +0300 [thread overview]
Message-ID: <aAPLygDGs6SoBZEv@black.fi.intel.com> (raw)
In-Reply-To: <CANiq72m5YW1aL+mAg4tcUwB7bKFC_4ZSGyeD8Z+mKzyPYG830g@mail.gmail.com>
On Sat, Apr 19, 2025 at 11:17:33AM +0200, Miguel Ojeda wrote:
> On Sat, Apr 19, 2025 at 1:50 AM Mauro Carvalho Chehab
> <mchehab+huawei@kernel.org> wrote:
> >
> > +*.pyc
> > *.patch
>
> I think the list is intended to be sorted.
+1, I told already twice, I dunno if my messages were seen.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-04-19 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 23:50 [PATCH v3 0/4] Don't create Python bytecode when building the kernel Mauro Carvalho Chehab
2025-04-18 23:50 ` [PATCH v3 1/4] docs: Makefile: get rid of KERNELDOC_CONF env variable Mauro Carvalho Chehab
2025-04-18 23:50 ` [PATCH v3 2/4] Makefile: move KERNELDOC macro to the main Makefile Mauro Carvalho Chehab
2025-04-18 23:50 ` [PATCH v3 3/4] scripts/kernel-doc.py: don't create *.pyc files Mauro Carvalho Chehab
2025-04-18 23:50 ` [PATCH v3 4/4] .gitignore: ignore Python compiled bytecode Mauro Carvalho Chehab
2025-04-19 9:17 ` Miguel Ojeda
2025-04-19 9:25 ` Miguel Ojeda
2025-04-19 16:14 ` Andy Shevchenko [this message]
2025-04-19 16:14 ` [PATCH v3 0/4] Don't create Python bytecode when building the kernel Andy Shevchenko
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=aAPLygDGs6SoBZEv@black.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=corbet@lwn.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=lizhijian@fujitsu.com \
--cc=masahiroy@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=tamird@gmail.com \
--cc=vegard.nossum@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.