git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Git Mailing list <git@vger.kernel.org>
Subject: man page for "git remote set-url" seems confusing/contradictory
Date: Mon, 16 Apr 2018 05:43:59 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.21.1804160538100.3564@localhost.localdomain> (raw)


  never had cause to examine "git remote set-url" before so i'm a bit
puzzled by this part of the man page:

  set-url

  Changes URLs for the remote. Sets first URL for remote
  <name> that matches regex <oldurl> ...

  With --push, push URLs are manipulated instead of fetch URLs.
 .. snip ...

  Note that the push URL and the fetch URL, even though they can be
  set differently, must still refer to the same place. What you pushed to
  the push URL should be what you would see if you immediately fetched
  from the fetch URL. If you are trying to fetch from one place (e.g.
  your upstream) and push to another (e.g. your publishing
  repository), use two separate remotes.

i don't understand how you can clearly set the fetch and push URLs of
a remote independently, while the man page nonetheless insists that
"even though they can be set differently, must still refer to the same
place". how can they be set differently yet still must refer to the
same place?

  i suspect i'll have a couple more questions related to this shortly
after i do a bit more reading.

rday

             reply	other threads:[~2018-04-16 12:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 12:43 Robert P. J. Day [this message]
2018-04-16 16:14 ` man page for "git remote set-url" seems confusing/contradictory Andreas Schwab
2018-04-16 16:19   ` Robert P. J. Day
2018-04-16 18:20     ` Jacob Keller
2018-04-16 23:13       ` Junio C Hamano
2018-04-17  1:01         ` Jacob Keller
2018-04-17 15:34         ` Robert P. J. Day
2018-04-17 17:41           ` Jacob Keller
2018-04-18  0:06             ` Junio C Hamano
2018-04-18 20:56               ` Todd Zullinger
2018-04-19  4:17                 ` Martin Ågren
2018-04-19 17:32                   ` [PATCH] doc/clone: update caption for GIT URLS cross-reference Todd Zullinger

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=alpine.LFD.2.21.1804160538100.3564@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --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).