From: "Lehua Ding" <lehua.ding@rivai.ai>
To: "Martin Jambor" <mjambor@suse.cz>, gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "juzhe.zhong" <juzhe.zhong@rivai.ai>,
jeffreyalaw <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] mklog: Add --append option to auto add generate ChangeLog to patch file
Date: Fri, 21 Jul 2023 18:57:04 +0800 [thread overview]
Message-ID: <24DB9A3E56C25E7E+tencent_F4D7FF335DC874F561BBCF9C3E766F1FE108@qq.com> (raw)
In-Reply-To: <ri65y6dlh6f.fsf@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 278 bytes --]
Hi Martin,
By the way, is there a standard format required for these Python files?
I see that other Python files have similar format error when checked
using flake8. If so, it feels necessary to configure a git hook on git server
to do this check.
Best,
Lehua
next prev parent reply other threads:[~2023-07-21 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 4:01 Lehua Ding
2023-07-12 16:04 ` Jeff Law
2023-07-13 3:29 ` Lehua Ding
2023-07-21 9:58 ` Martin Jambor
2023-07-21 10:22 ` =?gb18030?B?TGVodWEgRGluZw==?=
2023-07-21 10:39 ` Martin Jambor
2023-07-21 10:45 ` =?gb18030?B?TGVodWEgRGluZw==?=
2023-07-21 10:57 ` Lehua Ding [this message]
2023-07-21 11:56 ` Martin Jambor
2023-07-21 14:43 ` Lehua Ding
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=24DB9A3E56C25E7E+tencent_F4D7FF335DC874F561BBCF9C3E766F1FE108@qq.com \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=mjambor@suse.cz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).