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

Re: Incorrect branch information after fetching (local branch != remote branch)

From
Bagas Sanjaya <bagasdotme@gmail.com>
Date
May 3, 2022, 06:42 UTC
Message-ID
<bcb069c7-f104-a494-1862-30709dc6f8a0@gmail.com>
In-Reply-To
<xmqq7d73rwnq.fsf@gitster.g>
On 5/3/22 12:51, Junio C Hamano wrote:
Show 16 quoted lines
> The verbose report left by "git fetch" tells us what branch they
> have is used to update what branch we have, so I think this is
> pretty much expected.
> 
> I am puzzled by your mention of 'net-next' (local).
> 
> You may have
> 
>     [branch "net-next"]
>         remote = net-next
> 	merge = master
> 
> and that is where your expectation on the local may be coming from,
> but it wouldn't be all that relevant to "git fetch". The update of
> the local branch will happen long after "git fetch" is done.
> 
Ah I see.

So the left-hand side of verbose report (local branch) is actually the value of branch."net-next".merge, right?

-- 
An old man doll... just what I always wanted! - Clara
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 4 in “Incorrect branch information after fetching (local branch != remote branch)”
  1. Bagas SanjayaMay 3, 2022
  2. Junio C HamanoMay 3, 2022
  3. Bagas SanjayaMay 3, 2022
  4. Junio C HamanoMay 3, 2022

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.