gitk doesn't always shows boths tags in "gitk tag1..tag2"
For a cloned BOINC git tree :
$> git clone git://boinc.berkeley.edu/boinc.git
the following 2 commands shows both starting and ending revisions :
$> gitk client_release_7.0.41..client_release_7.0.42 $> gitk client_release_7.0.43..client_release_7.0.44
however this command doesn't show the tag "client_release_7.0.44" :
$> gitk client_release_7.0.44..client_release_7.0.45
Now I'm wondering whether this is a side effect of the developer model of BOINC or an issue in gitk ?
Signature · 3 lines
MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
Hi Toralf,
Quoted 5 lines · Toralf Förster
$> git clone
git://boinc.berkeley.edu/boinc.gitthe following 2 commands shows both starting and ending revisions :
$> gitk client_release_7.0.41..client_release_7.0.42
gitk is running something similar to
git log --graph --decorate --boundary --oneline <revs>
In this example, that means 7.0.41 is shown with an open circle because it is at the boundary of the requested commit set (it is not in that set and one of its children is).
[...]
Quoted 3 lines
however this command doesn't show the tag "client_release_7.0.44" :
$> gitk client_release_7.0.44..client_release_7.0.45
As you guessed, 7.0.45 seems to live in a different area of history. :) I don't know why it was built that way --- there may or may not be a good reason.
"gitk --simplify-by-decoration client_release_7.0.44...client_release_7.0.45" can help to compare the positions of the two tags in history.
Thanks for a fun example.
Jonathan
Quoted 1 line · Jonathan Nieder
As you guessed, 7.0.45 seems to live in a different area of history. :)
Well, seems be point to the root cause ..
BTW
$> gitk --simplify-by-decoration client_release_7.0.44..client_release_7.0.45
only 3 rows in the main window where
$> gitk client_release_7.0.44..client_release_7.0.45
shows 468 rows.
Thx for the quick answer :-)
Signature · 3 lines
MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
Quoted 11 lines · Toralf Förster
Quoted 1 line · Jonathan Nieder
As you guessed, 7.0.45 seems to live in a different area of history. :)
Well, seems be point to the root cause ..
BTW
$> gitk --simplify-by-decoration client_release_7.0.44..client_release_7.0.45only 3 rows in the main window where
$> gitk client_release_7.0.44..client_release_7.0.45
Easiest to look at
gitk --simplify-by-decoration client_release_7.0.44...client_release_7.0.45
(three dots --- search for "symmetric difference" in gitrevisions(7) for details).
Ciao,
Jonathan