public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: 丁乐华 <lehua.ding@rivai.ai>, jeffreyalaw <jeffreyalaw@gmail.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "Martin Jambor" <mjambor@suse.cz>
Subject: Re: Re: PING^2 [PATCH] mklog: fix bugs of --append option
Date: Mon, 7 Aug 2023 17:22:33 +0800	[thread overview]
Message-ID: <B16EB025E2082F56+202308071722330997993@rivai.ai> (raw)
In-Reply-To: <631ADD7FEB9B1EC6+tencent_D3E0DA6A661E19A89E7C3785B3DBEEFF2305@qq.com>

[-- Attachment #1: Type: text/plain, Size: 464 bytes --]

Hi, Jeff.
Could you help with this patch?

With this patch, we don't need to manually copy commit log.

With ../contrib/mklog.py -a patch

It will automatically copy to the commit log which is useful when sending patches.

Thanks.


juzhe.zhong@rivai.ai
 
From: Lehua Ding
Date: 2023-08-03 20:08
To: jeffreyalaw; gcc-patches
CC: juzhe.zhong; Martin Jambor
Subject: Re: PING^2 [PATCH] mklog: fix bugs of --append option
Gentle PING^2, thanks!


      reply	other threads:[~2023-08-07  9:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 12:08 Lehua Ding
2023-08-07  9:22 ` juzhe.zhong [this message]

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=B16EB025E2082F56+202308071722330997993@rivai.ai \
    --to=juzhe.zhong@rivai.ai \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=lehua.ding@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).