From: Daniele Sassoli <danielesassoli@gmail•com>
To: Junio C Hamano <gitster@pobox•com>, Elijah Newren <newren@gmail•com>
Cc: Daniele Sassoli via GitGitGadget <gitgitgadget@gmail•com>,
git@vger•kernel.org
Subject: Re: [PATCH v2] doc:clarify which remotes can be used when contributing
Date: Tue, 26 Aug 2025 07:50:24 +0100 [thread overview]
Message-ID: <4cc62d0c-eff7-4d8b-8f30-28c7d9064ce4@gmail.com> (raw)
In-Reply-To: <xmqqtt1vs77x.fsf@gitster.g>
On 25/08/2025 17:21, Junio C Hamano wrote:
> Elijah Newren <newren@gmail•com> writes:
>
>> On Sat, Aug 23, 2025 at 2:12 AM Daniele Sassoli via GitGitGadget
>> <gitgitgadget@gmail•com> wrote:
>>> From: Daniele Sassoli <danielesassoli@gmail•com>
>>>
>>> The docs mostly point to using git/git as one's remote, however, when it
>>> comes to Sending a PR to GitGitGadget section, the reader is told to use
>>> gitgitgadget/git, with no mention of git/git, potentially leading to
>>> some confusion.
>>> ...
>> This version looks good to me; thanks!
> Thanks both. I'll queue it after reritling.
>
>> doc: clarify which remotes can be used with GitGitGadget
> The only reason why you need to even "use" remote is because you are
> using GGG; othrewise you would not even be using any when sending
> your contribution in, so "when contributing" somewhat misses the
> point.
Makes sense, thanks for your help.
>
>
prev parent reply other threads:[~2025-08-26 6:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 19:14 [PATCH] doc:clarify which remotes can be used when contributing Daniele Sassoli via GitGitGadget
2025-08-19 21:19 ` Junio C Hamano
2025-08-20 14:07 ` Daniele Sassoli
2025-08-20 21:16 ` Junio C Hamano
2025-08-22 9:14 ` Daniele Sassoli
2025-08-22 17:56 ` Junio C Hamano
2025-08-22 18:45 ` Elijah Newren
2025-08-23 9:12 ` [PATCH v2] " Daniele Sassoli via GitGitGadget
2025-08-25 15:39 ` Elijah Newren
2025-08-25 16:21 ` Junio C Hamano
2025-08-26 6:50 ` Daniele Sassoli [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=4cc62d0c-eff7-4d8b-8f30-28c7d9064ce4@gmail.com \
--to=danielesassoli@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitgitgadget@gmail$(echo .)com \
--cc=gitster@pobox$(echo .)com \
--cc=newren@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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