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

Re: cannot see git-fetch result in gitk

From
Jakub Narebski <jnareb@gmail.com>
Date
Dec 1, 2007, 13:55 UTC
Message-ID
<m3zlwuwmce.fsf@roke.D-201>
In-Reply-To
<475154DB.4040606@imap.cc>
Tilman Schmidt <tilman@imap.cc> writes:
Show 13 quoted lines
> I'm still learning my way around git and trying to understand how it
> works. So after reading
>   howto/rebase-from-internal-branch.txt
> I wanted to try and understand the command sequence
> 
> git fetch origin
> git rebase FETCH_HEAD
> 
> by looking at what it does with gitk. But after the first command I do
> not see any change at all in gitk. Only after the second one do the
> newly fetched objects appear in the gitk display.
> 
> Simple question: why?

Did you run just "gitk"? By default gitk displays only current branch, while git-fetch changes remote-tracking branches only. Try "gitk --all", or "gitk origin/master ..." enumerating explicitely all remote branches.

-- 
Jakub Narebski
Poland
Previous: Tilman SchmidtNext: Tilman Schmidt
Message 2 of 3 in “cannot see git-fetch result in gitk”
  1. Tilman SchmidtDec 1, 2007
  2. Jakub NarebskiDec 1, 2007
  3. Tilman SchmidtDec 2, 2007

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.