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

Re: [PATCH] git-fetch: Allow branch."branchname".remote=.

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Oct 13, 2006, 11:27 UTC
Message-ID
<Pine.LNX.4.63.0610131324090.14200@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<8aa486160610130208s67ea0746o8a54910860b3fb78@mail.gmail.com>
Hi,
On Fri, 13 Oct 2006, Santi wrote:
Show 8 quoted lines
> For example, in git.git you could have:
> 
> [branch "next"]
>   remote="."
>   merge=master
> 
> so the default merge in the next branch is the master branch in the
> local repository.

There is a subtle problem here. Up until now, "remote" meant a short cut. You either had a file with that name in .git/remotes/ or .git/branches, or an entry in the config (remote.<name>.url).

You use it differently here, designating the URL instead of the remote. I'd rather have it point to a real remote.

Ciao, Dscho

Previous: SantiNext: Jakub Narebski
Message 4 of 7 in “git-fetch: Allow branch."branchname".remote=.”
  1. git-fetch: Allow branch."branchname".remote=.Santi Béjar, Oct 13, 2006
  2. Junio C HamanoOct 13, 2006
  3. SantiOct 13, 2006
  4. Johannes SchindelinOct 13, 2006
  5. Jakub NarebskiOct 13, 2006
  6. Johannes SchindelinOct 13, 2006
  7. Jakub NarebskiOct 13, 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.