From: Junio C Hamano <gitster@pobox.com>
To: Matthias Goergens <matthias.goergens@gmail.com>
Cc: git@vger.kernel.org, "Niklas Cassel" <cassel@kernel.org>,
"Bence Ferdinandy" <bence@ferdinandy.com>,
"Philip Oakley" <philipoakley@iee.email>,
"Jean-Noël Avila" <jn.avila@free.fr>
Subject: Re: [PATCH v2] doc: remote: say that it only affects the local repository
Date: Tue, 29 Sep 2026 09:28:25 -0700 [thread overview]
Message-ID: <xmqqld8khviu.fsf@gitster.g> (raw)
In-Reply-To: <20260929120010.840402-1-matthias.goergens@gmail.com> (Matthias Goergens's message of "Tue, 29 Sep 2026 20:00:10 +0800")
Matthias Goergens <matthias.goergens@gmail.com> writes:
> diff --git a/Documentation/git-remote.adoc b/Documentation/git-remote.adoc
> index eaae30aa88..315100409d 100644
> --- a/Documentation/git-remote.adoc
> +++ b/Documentation/git-remote.adoc
> @@ -28,6 +28,11 @@ DESCRIPTION
>
> Manage the set of repositories ("remotes") whose branches you track.
>
> +`git remote` changes only the local repository, i.e. its configuration
> +and its refs, and never modifies a remote repository. Some subcommands,
> +such as `show`, `prune`, `update` and `set-head --auto`, contact a
> +remote repository to read from it.
> +
I would not have minded having additional text in descriptions for
individual operations like 'set-head' and 'prune' that might be misread
to work on the other side, but the description above is very clear and
we may not need anything extra.
I also like the second sentence, mentioning that some commands read
from the remote. It implicitly stresses that nobody writes to the
remote.
Thanks.
prev parent reply other threads:[~2026-09-29 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 5:50 [PATCH] doc: clarify that set-head does not change the remote's HEAD Matthias Goergens
2026-09-28 19:01 ` Junio C Hamano
2026-09-29 12:00 ` [PATCH v2] doc: remote: say that it only affects the local repository Matthias Goergens
2026-09-29 16:28 ` Junio C Hamano [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=xmqqld8khviu.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bence@ferdinandy.com \
--cc=cassel@kernel.org \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
--cc=matthias.goergens@gmail.com \
--cc=philipoakley@iee.email \
/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