Thread (9 messages) flat view 9 messages, 4 authors, 2016-06-15

Re: [PATCH] git-remote: distinguish between default and configured URLs

From: John Keeping <hidden>
Date: 2016-06-15 22:55:47

Possibly related (same subject, not in this thread)

On Wed, Jan 16, 2013 at 11:14:48AM +0100, Michael J Gruber wrote:
The current output of "git remote -v" does not distinguish between
explicitly configured push URLs and those coming from fetch lines.

Revise the output so so that URLs are distinguished by their labels:

(fetch): fetch config used for fetching only
(fetch/push): fetch config used for fetching and pushing
(fetch fallback/push): fetch config used for pushing only
(fetch fallback): fetch config which is unused
(push): push config used for pushing
How does this interact with url.<base>.pushInsteadOf?

I have a global rule to convert git:// URLs to ssh:// for pushing:

    [url "git@example.com:"]
        pushInsteadOf = git://example.com/

With only a URL configured for a remote (no pushURL), I get (with Git
1.8.1):

    origin git://example.com/repository.git (fetch)
    origin git@example.com:repository.git (push)
From the original discussion in this thread, I think that if I did
"git remote set-url --add --push <url>" it would replace my current push
URL, and the change to "(fetch/push)" doesn't help in this case.

Should there be special handling for pushInsteadOf here?


John
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help