Re: defined behaviour for multiple urls for a remote
- From
Sitaram Chamarty <sitaramc@gmail.com>
- Date
- Oct 14, 2011, 14:01 UTC
- Message-ID
- <CAMK1S_jW5Fgv7j2w=xu8MMe_gaFFZNe+W4+Bvf1OrMR2rXQhCQ@mail.gmail.com>
- In-Reply-To
- <loom.20111014T113208-660@post.gmane.org>
On Fri, Oct 14, 2011 at 3:06 PM, Kirill Likhodedov <Kirill.Likhodedov@jetbrains.com> wrote:
Show 14 quoted lines
> 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... :-)