{"thread":{"id":"28671","subject":"defined behaviour for multiple urls for a remote","startedAt":"2011-10-14T07:07:51Z","lastAt":"2011-10-17T03:41:42Z","messageCount":4,"participants":["Sitaram Chamarty","Kirill Likhodedov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"177614","messageId":"CAMK1S_jZJuqC6_-eVT7LJFh+DEphbsypS6f4nRb6Qc4-xBa_wQ@mail.gmail.com","threadId":"28671","inReplyTo":null,"subject":"defined behaviour for multiple urls for a remote","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2011-10-14T07:07:51Z","receivedAt":"2011-10-14T07:07:51Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"Hi,\n\nWhat's the defined behaviour if I do this:\n\n[remote \"both\"]\n\turl = https://code.google.com/p/gitolite/\n url = git@github.com:sitaramc/gitolite.git\n\nI know what I'm seeing (a fetch only goes to the first URL, and does a\nHEAD->FETCH_HEAD because I didn't provide a refspec line, while a push\nseems to push all to both), but I was curious what the official\nposition is, because I couldn't find it in the docs.\n\n-- \nSitaram\n"},{"id":"177631","messageId":"loom.20111014T113208-660@post.gmane.org","threadId":"28671","inReplyTo":"CAMK1S_jZJuqC6_-eVT7LJFh+DEphbsypS6f4nRb6Qc4-xBa_wQ@mail.gmail.com","subject":"Re: defined behaviour for multiple urls for a remote","fromName":"Kirill Likhodedov","fromEmail":"kirill.likhodedov@jetbrains.com","sentAt":"2011-10-14T09:36:10Z","receivedAt":"2011-10-14T09:36:10Z","isPatch":false,"sender":{"key":"kirill.likhodedov@jetbrains.com","avatar":"https://gravatar.com/avatar/9fd55d2a110e8e96deb3ed7b503d7f3b9b5b1ed5ca9ef6683c15525b11b94e63?d=mp&s=160"},"body":"Sitaram Chamarty gmail.com> writes:\n\n> What's the defined behaviour if I do this:\n> \n> [remote \"both\"]\n> \turl = https://code.google.com/p/gitolite/\n> url = git github.com:sitaramc/gitolite.git\n> \n> I know what I'm seeing (a fetch only goes to the first URL, and does a\n> HEAD->FETCH_HEAD because I didn't provide a refspec line, while a push\n> seems to push all to both), but I was curious what the official\n> position is, because I couldn't find it in the docs.\n\nPlease see the message from Linus about that: http://marc.info/?l=git&m=116231242118202&w=2\n\nYou also may check how Git understands your remotes by running\n git remote -v\nIt will show, where it is going to fetch from and push to.\n\nI agree though, that documentation should be updated.\n"},{"id":"177646","messageId":"CAMK1S_jW5Fgv7j2w=xu8MMe_gaFFZNe+W4+Bvf1OrMR2rXQhCQ@mail.gmail.com","threadId":"28671","inReplyTo":"loom.20111014T113208-660@post.gmane.org","subject":"Re: defined behaviour for multiple urls for a remote","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2011-10-14T14:01:43Z","receivedAt":"2011-10-14T14:01:43Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Fri, Oct 14, 2011 at 3:06 PM, Kirill Likhodedov\n wrote:\n> Sitaram Chamarty gmail.com> writes:\n>\n>> What's the defined behaviour if I do this:\n>>\n>> [remote \"both\"]\n>>       url = https://code.google.com/p/gitolite/\n>>         url = git github.com:sitaramc/gitolite.git\n>>\n>> I know what I'm seeing (a fetch only goes to the first URL, and does a\n>> HEAD->FETCH_HEAD because I didn't provide a refspec line, while a push\n>> seems to push all to both), but I was curious what the official\n>> position is, because I couldn't find it in the docs.\n>\n> Please see the message from Linus about that: http://marc.info/?l=git&m=116231242118202&w=2\n\ncool; thanks!\n\n> You also may check how Git understands your remotes by running\n>  git remote -v\n\nAah that's very clear!\n\n> It will show, where it is going to fetch from and push to.\n>\n> I agree though, that documentation should be updated.\n\nwell if it never came up once in the 5 years since Linus wrote that email... :-)\n"},{"id":"177829","messageId":"CAMK1S_jzMKqA2SQR_q+5xjG_-CFM86cL0QaGvx-TA_sBC=Vh+g@mail.gmail.com","threadId":"28671","inReplyTo":"loom.20111014T113208-660@post.gmane.org","subject":"Re: defined behaviour for multiple urls for a remote","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2011-10-17T03:41:42Z","receivedAt":"2011-10-17T03:41:42Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Fri, Oct 14, 2011 at 3:06 PM, Kirill Likhodedov\n wrote:\n> Sitaram Chamarty gmail.com> writes:\n>\n>> What's the defined behaviour if I do this:\n>>\n>> [remote \"both\"]\n>>       url = https://code.google.com/p/gitolite/\n>>         url = git github.com:sitaramc/gitolite.git\n>>\n>> I know what I'm seeing (a fetch only goes to the first URL, and does a\n>> HEAD->FETCH_HEAD because I didn't provide a refspec line, while a push\n>> seems to push all to both), but I was curious what the official\n>> position is, because I couldn't find it in the docs.\n>\n> Please see the message from Linus about that: http://marc.info/?l=git&m=116231242118202&w=2\n\ncool; thanks!\n\n> You also may check how Git understands your remotes by running\n>  git remote -v\n\nAah that's very clear!\n\n> It will show, where it is going to fetch from and push to.\n>\n> I agree though, that documentation should be updated.\n\nwell in theory yes, but now that you mention it, 'git remote -v' is sufficient.\n"}]}