From: Calvin Wan <calvinwan@google.com>
To: git@vger.kernel.org
Cc: Calvin Wan <calvinwan@google.com>
Subject: [PATCH] Documentation: clarify multiple pushurls vs urls
Date: Mon, 6 Feb 2023 19:55:03 +0000 [thread overview]
Message-ID: <20230206195503.3113048-1-calvinwan@google.com> (raw)
While it is possible to define multiple `url` fields in a remote to
push to multiple remotes at once, it is preferable to achieve this by
defining multiple `pushurl` fields.
Defining multiple `url` fields can cause confusion for users since
running `git config remote.<remote>.url` returns the last defined url
which doesn't align with the url `git fetch <remote>` uses (the first).
Add documentation to clarify how fetch interacts with multiple urls
and the recommended method to push to multiple remotes.
Signed-off-by: Calvin Wan <calvinwan@google.com>
---
Documentation/urls-remotes.txt | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/urls-remotes.txt b/Documentation/urls-remotes.txt
index 86d0008f94..61aaded645 100644
--- a/Documentation/urls-remotes.txt
+++ b/Documentation/urls-remotes.txt
@@ -33,7 +33,10 @@ config file would appear like this:
------------
The `<pushurl>` is used for pushes only. It is optional and defaults
-to `<URL>`.
+to `<URL>`. Additional pushurls can be defined to push to multiple
+remotes. While multiple URLs can be defined to achieve the same
+outcome, this is not recommended since fetch only uses the first
+defined URL.
Named file in `$GIT_DIR/remotes`
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
2.39.1.519.gcb327c4b5f-goog
next reply other threads:[~2023-02-06 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 19:55 Calvin Wan [this message]
2023-02-06 20:11 ` [PATCH] Documentation: clarify multiple pushurls vs urls Ævar Arnfjörð Bjarmason
2023-02-06 21:12 ` Calvin Wan
2023-02-06 21:55 ` Ævar Arnfjörð Bjarmason
2023-02-06 23:00 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230206195503.3113048-1-calvinwan@google.com \
--to=calvinwan@google.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).