Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Yanteng Si <si.yanteng@linux.dev>
To: Dongliang Mu <dzm91@hust.edu.cn>, Alex Shi <seakeel@gmail.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>
Cc: hust-os-kernel-patches@googlegroups.com, llvm@lists.linux.dev
Subject: Re: [PATCH 0/2] Add the translation of documents in kbuild
Date: Mon, 21 Oct 2024 10:46:06 +0800	[thread overview]
Message-ID: <794f6563-019d-48f5-b96b-461f45ca7227@linux.dev> (raw)
In-Reply-To: <f38f12cd-2ea3-444c-8fbb-15ee0471a3cb@hust.edu.cn>




在 2024/10/21 10:13, Dongliang Mu 写道:
> On 2024/10/21 09:29, Alex Shi wrote:
>>
>> On 10/19/24 14:19, Dongliang Mu wrote:
>>> +to Jon and Alex.
>>>
>>> It seems that tocmd and cccmd does not work with cover letter. Any 
>>> suggestions?
>>>
>>>      tocmd ="`pwd`/scripts/get_maintainer.pl --nogit --norolestats 
>>> --nol"
>>>      cccmd ="`pwd`/scripts/get_maintainer.pl --nogit --norolestats 
>>> --nom"
>>>
>> Do you mean that to or cc cmd should give a name list for cover-letter?
>> I don't know if it's common needs, since some of people don't like to 
>> get every patches, maybe only the related patch is enough for them. 
>> But in another side, full name list is may wanted for others.
>>
>> Another interfere like this, is the 'git am 00*.patch', it failed on 
>> 0000-cover-letter as cover-letter is empty patch. I'm also not sure 
>> it's common needs...
>
> Yes. I realized it yesterday. And cover letter is not a patch. It 
> seems there is no need to handle cover letter specially. 
Hmm, By using git format-patch --to --cc, we can conveniently bundle a 
series
of related patches into email format and directly specify the reviewers, 
which
helps to keep communication clear and streamline the review process.

As for the cover letter, b4 does a great job, and we can use git am 
*.mbx instead
of git am 00*/*.patch.

Thanks,
Yanteng

      reply	other threads:[~2024-10-21  2:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 13:47 [PATCH 0/2] Add the translation of documents in kbuild Dongliang Mu
2024-10-18 13:47 ` [PATCH 1/2] docs/zh_CN: add the translation of kbuild/kbuild.rst Dongliang Mu
2024-10-19  6:19 ` [PATCH 0/2] Add the translation of documents in kbuild Dongliang Mu
2024-10-21  1:29   ` Alex Shi
2024-10-21  2:13     ` Dongliang Mu
2024-10-21  2:46       ` Yanteng Si [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=794f6563-019d-48f5-b96b-461f45ca7227@linux.dev \
    --to=si.yanteng@linux.dev \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=hust-os-kernel-patches@googlegroups.com \
    --cc=justinstitt@google.com \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=seakeel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox