threads / discuss / 32772

gitk doesn't always shows boths tags in "gitk tag1..tag2"

Subject: gitk doesn't always shows boths tags in "gitk tag1..tag2"

## tl;dr

4 messages between Jan 29, 2013 and Jan 29, 2013.

replies: 3people: 2as markdown or json

Toralf Förster· Jan 29, 2013, 19:40 UTC · lore
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 ?

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
Jonathan Nieder· Jan 29, 2013, 19:57 UTC · re: Toralf Förster · lore

Re: gitk doesn't always shows boths tags in "gitk tag1..tag2"

Hi Toralf,
Toralf Förster wrote:
Show 5 quoted lines
> $> 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 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).

[...]
> 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

Toralf Förster· Jan 29, 2013, 20:11 UTC · re: Jonathan Nieder · lore

Re: gitk doesn't always shows boths tags in "gitk tag1..tag2"

On 01/29/2013 08:57 PM, Jonathan Nieder wrote:
> 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 :-)
-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
Jonathan Nieder· Jan 29, 2013, 20:25 UTC · re: Toralf Förster · lore

Re: gitk doesn't always shows boths tags in "gitk tag1..tag2"

Toralf Förster wrote:
> On 01/29/2013 08:57 PM, Jonathan Nieder wrote:
Show 9 quoted lines
>> 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
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

← back to recent threads