From: Tilman Schmidt <tilman@imap.cc>
To: git@vger.kernel.org
Subject: cannot see git-fetch result in gitk
Date: Sat, 01 Dec 2007 13:34:35 +0100 [thread overview]
Message-ID: <475154DB.4040606@imap.cc> (raw)
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
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!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next reply other threads:[~2007-12-01 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 12:34 Tilman Schmidt [this message]
2007-12-01 13:55 ` cannot see git-fetch result in gitk Jakub Narebski
2007-12-02 15:15 ` Tilman Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=475154DB.4040606@imap.cc \
--to=tilman@imap.cc \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).