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

Re: [PATCH 3/3] fetch: optionally store the current remote information in the config

From
sean <seanlkml@sympatico.ca>
Date
Apr 30, 2006, 17:28 UTC
Message-ID
<BAYC1-PASMTP05AA5A3E9CB852B03EAC4DAEB00@CEZ.ICE>
In-Reply-To
<Pine.LNX.4.63.0604301859280.3977@wbgn013.biozentrum.uni-wuerzburg.de>

On Sun, 30 Apr 2006 19:09:18 +0200 (CEST) Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

> > Which head does git-pull then use to merge, all of them?
> 
> The first one.

Which can be confusing since you can only specify one "first one" in a remotes file (or .git/config) yet you can pull while having any random local branch being checkout out, each with a different merge branch being appropriate.

Show 11 quoted lines
> You are right. But you are also wrong. The patch uses
> 
> 	git-repo-config --get remote.$nick.url
> 
> which fails if there are more than one matching line. Note that 
> "--get-all" is used to get _all_ remote.$nick.pull lines...
> 
> But of course, Linus "built git-push in" so that multiple urls are 
> allowed and handled. It is probably confusing, if you can push but 
> cannot fetch with the same remote information... But then, I fail to see 
> how you could possibly specify the refspecs for the different urls.

Yeah, I was speaking only of git push, but see you were speaking of fetch.

Anyway, thanks for helping me understand your proposal, it seems flexible enough to handle just about any case one might want to throw at it.

Cheers, Sean

Previous: Johannes SchindelinNext: Junio C Hamano
Message 12 of 16 in “fetch: optionally store the current remote information in the config”
  1. 3/3 fetch: optionally store the current remote information in the configJohannes Schindelin, Apr 30, 2006
  2. Jakub NarebskiApr 30, 2006
  3. Johannes SchindelinApr 30, 2006
  4. Jakub NarebskiApr 30, 2006
  5. seanApr 30, 2006
  6. Johannes SchindelinApr 30, 2006
  7. seanApr 30, 2006
  8. Jakub NarebskiApr 30, 2006
  9. seanApr 30, 2006
  10. Jakub NarebskiApr 30, 2006
  11. Johannes SchindelinApr 30, 2006
  12. seanApr 30, 2006
  13. Junio C HamanoApr 30, 2006
  14. Junio C HamanoMay 2, 2006
  15. Johannes SchindelinMay 2, 2006
  16. Junio C HamanoMay 3, 2006

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.