From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Akira Yokosawa <akiyks@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] docs: Makefile: store __pycache__ at the output directory
Date: Fri, 25 Apr 2025 21:10:29 +0300 [thread overview]
Message-ID: <aAvQFen6D5ukjj-x@smile.fi.intel.com> (raw)
In-Reply-To: <1b9e7f34c1d99a27a8abb308da3221b4663b5693.1745539360.git.mchehab+huawei@kernel.org>
On Fri, Apr 25, 2025 at 08:08:53AM +0800, Mauro Carvalho Chehab wrote:
> Instead of blocking creation of *.pyc cache, store python
> cache under Documentation/output/__pycache__
Do we need the below in the commit message?
I think having statistics is enough and this can be moved to the cover letter.
> 109 directories, 634 files
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-04-25 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 0:08 [PATCH 0/1] Let Sphinx store cached bytecode under the output dir Mauro Carvalho Chehab
2025-04-25 0:08 ` [PATCH 1/1] docs: Makefile: store __pycache__ at the output directory Mauro Carvalho Chehab
2025-04-25 18:10 ` Andy Shevchenko [this message]
2025-04-28 23:57 ` Jonathan Corbet
2025-04-30 15:42 ` Mauro Carvalho Chehab
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=aAvQFen6D5ukjj-x@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.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;
as well as URLs for NNTP newsgroup(s).