threads / discuss / 28671
Subject: defined behaviour for multiple urls for a remote
Sitaram ChamartyHi,
What's the defined behaviour if I do this:
[remote "both"]
url = https://code.google.com/p/gitolite/
url = git@github.com:sitaramc/gitolite.gitI 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
Kirill LikhodedovRe: defined behaviour for multiple urls for a remote
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.
Sitaram ChamartyRe: defined behaviour for multiple urls for a remote
On Fri, Oct 14, 2011 at 3:06 PM, Kirill Likhodedov <Kirill.Likhodedov@jetbrains.com> wrote:
> 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
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... :-)
Sitaram ChamartyRe: defined behaviour for multiple urls for a remote
On Fri, Oct 14, 2011 at 3:06 PM, Kirill Likhodedov <Kirill.Likhodedov@jetbrains.com> wrote:
> 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
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.