defined behaviour for multiple urls for a remote

4 messages, 2 authors, 2016-06-15 · open the first message on its own page

defined behaviour for multiple urls for a remote

From: Sitaram Chamarty <hidden>
Date: 2016-06-15 22:52:15

Hi,

What's the defined behaviour if I do this:

[remote "both"]
	url = https://code.google.com/p/gitolite/
        url = git@github.com:sitaramc/gitolite.git

I know what I'm seeing (a fetch only goes to the first URL, and does a
HEAD->FETCH_HEAD because I didn't provide a refspec line, while a push
seems to push all to both), but I was curious what the official
position is, because I couldn't find it in the docs.

-- 
Sitaram

Re: defined behaviour for multiple urls for a remote

From: Kirill Likhodedov <hidden>
Date: 2016-06-15 22:52:15

Sitaram Chamarty <sitaramc <at> gmail.com> writes:
What's the defined behaviour if I do this:

[remote "both"]
	url = https://code.google.com/p/gitolite/
        url = git <at> github.com:sitaramc/gitolite.git

I know what I'm seeing (a fetch only goes to the first URL, and does a
HEAD->FETCH_HEAD because I didn't provide a refspec line, while a push
seems to push all to both), but I was curious what the official
position is, because I couldn't find it in the docs.
Please see the message from Linus about that: http://marc.info/?l=git&m=116231242118202&w=2

You also may check how Git understands your remotes by running
  git remote -v
It will show, where it is going to fetch from and push to.

I agree though, that documentation should be updated.

Re: defined behaviour for multiple urls for a remote

From: Sitaram Chamarty <hidden>
Date: 2016-06-15 22:52:15

On Fri, Oct 14, 2011 at 3:06 PM, Kirill Likhodedov
[off-list ref] wrote:
Sitaram Chamarty <sitaramc <at> gmail.com> writes:
quoted
What's the defined behaviour if I do this:

[remote "both"]
      url = https://code.google.com/p/gitolite/
        url = git <at> github.com:sitaramc/gitolite.git

I know what I'm seeing (a fetch only goes to the first URL, and does a
HEAD->FETCH_HEAD because I didn't provide a refspec line, while a push
seems to push all to both), but I was curious what the official
position is, because I couldn't find it in the docs.
Please see the message from Linus about that: http://marc.info/?l=git&m=116231242118202&w=2
cool; thanks!
You also may check how Git understands your remotes by running
 git remote -v
Aah that's very clear!
It will show, where it is going to fetch from and push to.

I agree though, that documentation should be updated.
well if it never came up once in the 5 years since Linus wrote that email... :-)

Re: defined behaviour for multiple urls for a remote

From: Sitaram Chamarty <hidden>
Date: 2016-06-15 22:52:16

On Fri, Oct 14, 2011 at 3:06 PM, Kirill Likhodedov
[off-list ref] wrote:
Sitaram Chamarty <sitaramc <at> gmail.com> writes:
quoted
What's the defined behaviour if I do this:

[remote "both"]
      url = https://code.google.com/p/gitolite/
        url = git <at> github.com:sitaramc/gitolite.git

I know what I'm seeing (a fetch only goes to the first URL, and does a
HEAD->FETCH_HEAD because I didn't provide a refspec line, while a push
seems to push all to both), but I was curious what the official
position is, because I couldn't find it in the docs.
Please see the message from Linus about that: http://marc.info/?l=git&m=116231242118202&w=2
cool; thanks!
You also may check how Git understands your remotes by running
 git remote -v
Aah that's very clear!
It will show, where it is going to fetch from and push to.

I agree though, that documentation should be updated.
well in theory yes, but now that you mention it, 'git remote -v' is sufficient.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help