git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jan 29, 2013, 19:57 UTC
Message-ID
<20130129195718.GD18266@google.com>
In-Reply-To
<510825B2.6070805@gmx.de>
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

Previous: Toralf FörsterNext: Toralf Förster
Message 2 of 4 in “gitk doesn't always shows boths tags in "gitk tag1..tag2"”
  1. Toralf FörsterJan 29, 2013
  2. Jonathan NiederJan 29, 2013
  3. Toralf FörsterJan 29, 2013
  4. Jonathan NiederJan 29, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.