From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Daniele Sassoli via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Daniele Sassoli <danielesassoli@gmail.com>
Subject: Re: [PATCH v2] doc:clarify which remotes can be used when contributing
Date: Mon, 25 Aug 2025 09:21:06 -0700 [thread overview]
Message-ID: <xmqqtt1vs77x.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BHCQjFtpr8meUqhGEiTgsqZ9KTWcpLYA8yEPUsCAceAGg@mail.gmail.com> (Elijah Newren's message of "Mon, 25 Aug 2025 08:39:00 -0700")
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.
next prev parent reply other threads:[~2025-08-25 16:21 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 [this message]
2025-08-26 6:50 ` Daniele Sassoli
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=xmqqtt1vs77x.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=danielesassoli@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=newren@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).