From: Andreas Schwab <schwab@linux-m68k.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: man page for "git remote set-url" seems confusing/contradictory
Date: Mon, 16 Apr 2018 18:14:58 +0200 [thread overview]
Message-ID: <87y3hn5drx.fsf@linux-m68k.org> (raw)
In-Reply-To: <alpine.LFD.2.21.1804160538100.3564@localhost.localdomain> (Robert P. J. Day's message of "Mon, 16 Apr 2018 05:43:59 -0700 (PDT)")
On Apr 16 2018, "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
> 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?
They could be using different transport methods. For example, for
fetching the unauthenticated git: method could be used, but for pushing
an authenticated method like ssh: is usually needed.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2018-04-16 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 12:43 man page for "git remote set-url" seems confusing/contradictory Robert P. J. Day
2018-04-16 16:14 ` Andreas Schwab [this message]
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=87y3hn5drx.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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).