From: "Gustavo Velasco-Hernández via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: "Gustavo Velasco-Hernández" <gustavo.velascoh@gmail.com>,
"Velasco-Hernandez,
Gustavo" <Gustavo.Velasco-Hernandez@netapp.com>
Subject: [PATCH v2] docs: update description for '--mirror' option for 'git push'
Date: Tue, 16 Sep 2025 16:03:48 +0000 [thread overview]
Message-ID: <pull.2028.v2.git.git.1758038628948.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2028.git.git.1754922884439.gitgitgadget@gmail.com>
From: "Velasco-Hernandez, Gustavo" <Gustavo.Velasco-Hernandez@netapp.com>
The current description considers only created, updated or deleted refs
locally. However it does not address the case where new refs were created
on the remote end, in which case, are also deleted. The description has
been reworded to describe what is removed, updated or added. (Based on
Junio feedback)
Signed-off-by: Gustavo Velasco-Hernandez <gustavo.velascoh@gmail.com>
---
Docs: Update description for '--mirror' option for 'git push'
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2028%2Fgustavovelascoh%2Fgit-push-update-docs-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2028/gustavovelascoh/git-push-update-docs-v2
Pull-Request: https://github.com/git/git/pull/2028
Range-diff vs v1:
1: 2be0bf6e73 ! 1: ab077544b6 docs: update description for '--mirror' option for 'git push'
@@ Commit message
The current description considers only created, updated or deleted refs
locally. However it does not address the case where new refs were created
- on the remote end, in which case, are also deleted.
+ on the remote end, in which case, are also deleted. The description has
+ been reworded to describe what is removed, updated or added. (Based on
+ Junio feedback)
Signed-off-by: Gustavo Velasco-Hernandez <gustavo.velascoh@gmail.com>
## Documentation/git-push.adoc ##
@@ Documentation/git-push.adoc: already exists on the remote side.
- be mirrored to the remote repository. Newly created local
- refs will be pushed to the remote end, locally updated refs
- will be force updated on the remote end, and deleted refs
+ Instead of naming each ref to push, specifies that all
+ refs under `refs/` (which includes but is not
+ limited to `refs/heads/`, `refs/remotes/`, and `refs/tags/`)
+- be mirrored to the remote repository. Newly created local
+- refs will be pushed to the remote end, locally updated refs
+- will be force updated on the remote end, and deleted refs
- will be removed from the remote end. This is the default
- if the configuration option `remote.<remote>.mirror` is
- set.
-+ will be removed from the remote end. Any ref existing
-+ in the remote end, but not locally, will be removed too.
-+ This is the default if the configuration option
-+ `remote.<remote>.mirror` is set.
++ be mirrored to the remote repository. This overwrites the
++ refs at the remote by (1) removing what is only at the remote,
++ (2) force-updating what both ends of the connection have, and
++ (3) adding what only exists locally. This is the default if
++ the configuration option `remote.<remote>.mirror` is set.
-n::
--dry-run::
Documentation/git-push.adoc | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/Documentation/git-push.adoc b/Documentation/git-push.adoc
index 5f5408e2c0..77ce4a27c8 100644
--- a/Documentation/git-push.adoc
+++ b/Documentation/git-push.adoc
@@ -163,12 +163,11 @@ already exists on the remote side.
Instead of naming each ref to push, specifies that all
refs under `refs/` (which includes but is not
limited to `refs/heads/`, `refs/remotes/`, and `refs/tags/`)
- be mirrored to the remote repository. Newly created local
- refs will be pushed to the remote end, locally updated refs
- will be force updated on the remote end, and deleted refs
- will be removed from the remote end. This is the default
- if the configuration option `remote.<remote>.mirror` is
- set.
+ be mirrored to the remote repository. This overwrites the
+ refs at the remote by (1) removing what is only at the remote,
+ (2) force-updating what both ends of the connection have, and
+ (3) adding what only exists locally. This is the default if
+ the configuration option `remote.<remote>.mirror` is set.
-n::
--dry-run::
base-commit: a483264b01b977f3e65a4419103c21e6af7412a2
--
gitgitgadget
next prev parent reply other threads:[~2025-09-16 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 14:34 [PATCH] docs: update description for '--mirror' option for 'git push' Gustavo Velasco-Hernández via GitGitGadget
2025-08-11 16:41 ` Junio C Hamano
2025-09-16 16:03 ` Gustavo Velasco-Hernández via GitGitGadget [this message]
2025-09-16 17:19 ` [PATCH v2] " Junio C Hamano
2025-09-16 20:04 ` Kristoffer Haugsbakk
2025-09-18 20:58 ` Kristoffer Haugsbakk
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=pull.2028.v2.git.git.1758038628948.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=Gustavo.Velasco-Hernandez@netapp.com \
--cc=git@vger.kernel.org \
--cc=gustavo.velascoh@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).