From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] format-patch: give an overview of what a "patch" message is
Date: Fri, 26 Mar 2021 15:26:25 +0700 [thread overview]
Message-ID: <7c0aabe0-9240-950e-912f-0a195db7a144@gmail.com> (raw)
In-Reply-To: <xmqqmturuh8o.fsf@gitster.g>
On 26/03/21 03.10, Junio C Hamano wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
>
>> The text says something called a "patch" is prepared one for each
>> commit, it is suitable for e-mail submission, and "am" is the
>> command to use it, but does not say what the "patch" really is. The
>> description in the page also refers to "three-dash" line, but that
>> is totally unclear unless the reader is given a more detailed
>> overview of what the "patch" the first paragraph refers to.
>>
>> Co-authored-by: Junio C Hamano <gitster@pobox.com>
>> Signed-off-by: Junio C Hamano <gitster@pobox.com>
>> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
>> ---
>
> I do not think this was co-authored; you are forwarding somebody
> else's patch that was written without any input from you.
>
Oh dear...
Next time when I need to send patches forwarded from you (or others),
but not necessarily Co-authored-by, what should I do? Something like
this note below?
[forwarded from someone]
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-03-26 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 10:54 [PATCH] format-patch: give an overview of what a "patch" message is Bagas Sanjaya
2021-03-25 20:10 ` Junio C Hamano
2021-03-26 8:26 ` Bagas Sanjaya [this message]
2021-03-26 8:45 ` Jeff King
2021-03-26 22:41 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c0aabe0-9240-950e-912f-0a195db7a144@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).