{"thread":{"id":"11076","subject":"cannot see git-fetch result in gitk","startedAt":"2007-12-01T12:34:35Z","lastAt":"2007-12-02T15:15:56Z","messageCount":3,"participants":["Tilman Schmidt","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"61574","messageId":"475154DB.4040606@imap.cc","threadId":"11076","inReplyTo":null,"subject":"cannot see git-fetch result in gitk","fromName":"Tilman Schmidt","fromEmail":"tilman@imap.cc","sentAt":"2007-12-01T12:34:35Z","receivedAt":"2007-12-01T12:34:35Z","isPatch":false,"sender":{"key":"tilman@imap.cc","avatar":null},"body":"I'm still learning my way around git and trying to understand how it\nworks. So after reading\nhttp://www.kernel.org/pub/software/scm/git/docs/howto/rebase-from-internal-branch.txt\nI wanted to try and understand the command sequence\n\ngit fetch origin\ngit rebase FETCH_HEAD\n\nby looking at what it does with gitk. But after the first command I do\nnot see any change at all in gitk. Only after the second one do the\nnewly fetched objects appear in the gitk display.\n\nSimple question: why?\n\nThanks,\nTilman\n\n-- \nTilman Schmidt                          E-Mail: tilman@imap.cc\nBonn, Germany\nYes, I have searched Google!\n\n"},{"id":"61578","messageId":"m3zlwuwmce.fsf@roke.D-201","threadId":"11076","inReplyTo":"475154DB.4040606@imap.cc","subject":"Re: cannot see git-fetch result in gitk","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-12-01T13:55:53Z","receivedAt":"2007-12-01T13:55:53Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Tilman Schmidt <tilman@imap.cc> writes:\n\n> I'm still learning my way around git and trying to understand how it\n> works. So after reading\n>   howto/rebase-from-internal-branch.txt\n> I wanted to try and understand the command sequence\n> \n> git fetch origin\n> git rebase FETCH_HEAD\n> \n> by looking at what it does with gitk. But after the first command I do\n> not see any change at all in gitk. Only after the second one do the\n> newly fetched objects appear in the gitk display.\n> \n> Simple question: why?\n\nDid you run just \"gitk\"? By default gitk displays only current branch,\nwhile git-fetch changes remote-tracking branches only. Try \n\"gitk --all\", or \"gitk origin/master ...\" enumerating explicitely all\nremote branches.\n\n-- \nJakub Narebski\nPoland\n"},{"id":"61647","messageId":"4752CC2C.800@imap.cc","threadId":"11076","inReplyTo":"m3zlwuwmce.fsf@roke.D-201","subject":"Re: cannot see git-fetch result in gitk","fromName":"Tilman Schmidt","fromEmail":"tilman@imap.cc","sentAt":"2007-12-02T15:15:56Z","receivedAt":"2007-12-02T15:15:56Z","isPatch":false,"sender":{"key":"tilman@imap.cc","avatar":null},"body":"Am 01.12.2007 14:55 schrieb Jakub Narebski:\n> Did you run just \"gitk\"? By default gitk displays only current branch,\n\nThanks, that explains it. It might be a good idea to mention that\nin the manpage.\n\n> while git-fetch changes remote-tracking branches only. Try \n> \"gitk --all\", or \"gitk origin/master ...\" enumerating explicitely all\n> remote branches.\n\nOk, thanks, will try that next time git-fetch actually finds something\nto fetch. ;-)\n\n-- \nTilman Schmidt                          E-Mail: tilman@imap.cc\nBonn, Germany\nDiese Nachricht besteht zu 100% aus wiederverwerteten Bits.\nUngeöffnet mindestens haltbar bis: (siehe Rückseite)\n\n"}]}