git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: defined behaviour for multiple urls for a remote

From
Kirill Likhodedov <kirill.likhodedov@jetbrains.com>
Date
Oct 14, 2011, 09:36 UTC
Message-ID
<loom.20111014T113208-660@post.gmane.org>
In-Reply-To
<CAMK1S_jZJuqC6_-eVT7LJFh+DEphbsypS6f4nRb6Qc4-xBa_wQ@mail.gmail.com>
Sitaram Chamarty <sitaramc <at> gmail.com> writes:
Show 10 quoted lines
> 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.
Previous: Sitaram ChamartyNext: Sitaram Chamarty
Message 2 of 4 in “defined behaviour for multiple urls for a remote”
  1. Sitaram ChamartyOct 14, 2011
  2. Kirill LikhodedovOct 14, 2011
  3. Sitaram ChamartyOct 14, 2011
  4. Sitaram ChamartyOct 17, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.