Re: man page for "git remote set-url" seems confusing/contradictory

From: Robert P. J. Day <rpjday@crashcourse.ca>
Date: Apr 17, 2018, 15:34 UTC
Message-ID: <alpine.LFD.2.21.1804170831190.6019@localhost.localdomain>
In-Reply-To: <xmqqefjewxr4.fsf@gitster-ct.c.googlers.com>

On Tue, 17 Apr 2018, Junio C Hamano wrote:

Show 15 quoted lines

> Jacob Keller <jacob.keller@gmail.com> writes:
>
> > Things won't work so well if you set the push url and fetch url to
> > different repositories. Git assumes that refs updated by "push"
> > will also be reflected via "fetch".
> >
> > I don't know offhand what will break, but likely something will.
> > For one, when you fetch again it will rewind your remotes after
> > the push.
>
> Exactly.  I still haven't fully embraced it myself, but for a long
> time, "git push" pretends as if it fetched from that remote and
> updates the corresponding remote tracking branches (if you have
> any), so you'll be inviting inconsistent behaviour if you set your
> fetch and push URLs pointing at two logically separate places.

  ... snip ...

  oh, i totally buy all that now, i'm just suggesting that the man
page might be tweaked to make that more obvious. in "man git-remote",
under "set-url", remember that it reads:

"Note that the push URL and the fetch URL, even though they can be set differently, must still refer to the same place."

  i think it would be useful to be more specific about what "can be
set differently" means, since a lot of readers might not immediately
appreciate that it means just, say, the transport protocols. it never
hurts to add that little bit of detail.

rday