I'm still learning my way around git and trying to understand how it
works. So after reading
http://www.kernel.org/pub/software/scm/git/docs/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?
Thanks,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Yes, I have searched Google!
Tilman Schmidt [off-list ref] writes:
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
Am 01.12.2007 14:55 schrieb Jakub Narebski:
Did you run just "gitk"? By default gitk displays only current branch,
Thanks, that explains it. It might be a good idea to mention that
in the manpage.
while git-fetch changes remote-tracking branches only. Try
"gitk --all", or "gitk origin/master ..." enumerating explicitely all
remote branches.
Ok, thanks, will try that next time git-fetch actually finds something
to fetch. ;-)
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)