Re: [PATCH v2 3/8] SubmittingPatches: mention GitGitGadget

> "Linus Arver via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
>> From: Linus Arver <linusa@google.com>
>>
>> Signed-off-by: Linus Arver <linusa@google.com>
>> ---
>>  Documentation/SubmittingPatches | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
>> index a33fe7e11f6..48b270b4c48 100644
>> --- a/Documentation/SubmittingPatches
>> +++ b/Documentation/SubmittingPatches
>> @@ -408,6 +408,10 @@ are optimized for the workflow of sending patches, avoiding many ways
>>  your existing e-mail client (often optimized for "multipart/*" MIME
>>  type e-mails) might render your patches unusable.
>>  
>> +NOTE: You can also use GitGitGadget (https://gitgitgadget.github.io/) to send in
>> +your patches. The discussion here focuses on using `format-patch` and
>> +`send-email`.
>> +
>>  People on the Git mailing list need to be able to read and
>>  comment on the changes you are submitting.  It is important for
>>  a developer to be able to "quote" your changes, using standard
>
> Rather than giving the URL and have the readers figure out how to
> use it for themselves, it would be more helpful to readers to refer
> them to MyFirstContrib document.
>
>     Note: we outline the procedure using `format-patch` plus
>     `send-email`, but you can also use GitGitGadget to send in your
>     patches (see MyFirstContribution document).