* Re: gitk refresh keeps showing dangling commits
[not found] <CAByu6UVWWW+5QKfVD30_LR4UF3991PLMRHGo6WWgrxOPXws0mQ@mail.gmail.com>
@ 2013-11-29 15:27 ` Thibault Kruse
2013-12-04 9:45 ` Gauthier Östervall
0 siblings, 1 reply; 2+ messages in thread
From: Thibault Kruse @ 2013-11-29 15:27 UTC (permalink / raw)
To: git
Hi,
my Ubuntu saucy version of gitk is 1.8.3.2-1 I believe.
I want to report what I believe is a bug. I have been using gitk for 3
years, and I use it to verify what I am doing in the shell.
In the version I use now, the behavior has changed.
When I do
mkdir temp
cd temp
git init
touch foo
git add foo
git commit -m 'foo'
echo "bar" > foo
git add foo
git commit -m 'foo'
gitk &
then I see gitk showing the foo and bar commits, so far so good. Then,
leaving gitk open, I do:
git reset --hard HEAD~1
and in gitk, I select "Reload"(Ctrl-F5), and I still see both commits,
not just commit foo. This is very annoying for me for doing rebases,
as I don't care about all the dangling commits left by my rebases, and
now I have to restart gitk each time to see a "clean" history.
I believe "Refresh"(F5) may still display such commits, but a reload
should display what I would get if I restarted gitk, which is just
displaying one commit in the above case.
cheers,
Thibault
^ permalink raw reply [flat|nested] 2+ messages in thread