git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: 王常新 <wchangxin824@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] typo: fix the typo 'neeed' into 'needed' in the comment under merge-ort.c
Date: Sat, 21 Oct 2023 15:12:19 +0700	[thread overview]
Message-ID: <1df77452-2355-400c-adbb-a04b2bc32602@gmail.com> (raw)
In-Reply-To: <xmqqfs25rzo1.fsf@gitster.g>

On 21/10/2023 00:06, Junio C Hamano wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
> 
>> On 20/10/2023 09:14, 王常新 wrote:
>>> It is my official name. But the email address is not a valid one. Should I rewrite the commit message?
>>>
>>
>> Please don't top-post, reply inline with appropriate context instead.
>>
>> Did you mean that you can't receive ML traffic on your @qq.com address?
>> If so, resend with your @gmail.com address as patch author (you need
>> to set user.name and user.email accordingly). 
> 
> Isn't that opposite from what we would normally recommend, though?
> 
> If the true authorship e-mail is in an environment where sending
> patches are inconvenient, you would still want to do your commits
> under the identity you want to appear in the final history of the
> project, so you do not futz with user.name and user.email; you'd
> send a message with in-body header that shows an extra From: line
> (followed by a blank line) that records the true authorship from an
> environment whose sender e-mail address may differ.
> 
> E.g.  You would see these fields in the e-mail heeader:
> 
> 	From: 王常新 <wchangxin824@gmail.com>
> 	Subject: [PATCH] merge-ort.c: comment typofix
> 
> and your message would begin like so (indented only for illustration
> purposes---the real one should be flushed to the left edge of the
> page):
> 
> 	From: 王常新 <real-email-address-of-mr-wang@do.ma.in>
> 
> 	There is 'needed' misspelt as 'neeed' in the source file;
> 	fix it.
> 
> 	Signed-off-by: 王常新 <real-email-address-of-mr-wang@do.ma.in>
> 
> This feature is designed so that other people, different from the
> author of the patch, can relay it to the recipient(s) while
> preserving the authorship information.
> 
> Although it is not needed in this case, you can override "Subject:"
> the same way with an in-body header, like so:
> 
> 	From: 王常新 <real-email-address-of-mr-wang@do.ma.in>
> 	Subject: real title of the patch to be used
> 
> 	There is 'needed' misspelt as 'neeed' in the source file;
> 	fix it.
> 
> 	Signed-off-by: 王常新 <real-email-address-of-mr-wang@do.ma.in>
> 
> and it would replace what we read from the Subject: e-mail header.

Thanks for the explanation! I was confused then...

-- 
An old man doll... just what I always wanted! - Clara


  reply	other threads:[~2023-10-21  8:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 12:24 [PATCH] typo: fix the typo 'neeed' into 'needed' in the comment under merge-ort.c 王常新
2023-10-19 17:05 ` Junio C Hamano
2023-10-20  2:14   ` 王常新
2023-10-20  7:41     ` Bagas Sanjaya
2023-10-20 17:06       ` Junio C Hamano
2023-10-21  8:12         ` Bagas Sanjaya [this message]
2023-10-20 16:44     ` Junio C Hamano
2023-10-21  1:22       ` 王常新
2023-10-21 17:26         ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2023-10-15 14:08 Wangchangxin via GitGitGadget

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=1df77452-2355-400c-adbb-a04b2bc32602@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=wchangxin824@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;
as well as URLs for NNTP newsgroup(s).