From: Jonathan Nieder <jrnieder@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: gitk doesn't always shows boths tags in "gitk tag1..tag2"
Date: Tue, 29 Jan 2013 12:25:18 -0800 [thread overview]
Message-ID: <20130129202518.GE18266@google.com> (raw)
In-Reply-To: <51082CFA.4050501@gmx.de>
Toralf Förster wrote:
> 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
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
prev parent reply other threads:[~2013-01-29 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 19:40 gitk doesn't always shows boths tags in "gitk tag1..tag2" Toralf Förster
2013-01-29 19:57 ` Jonathan Nieder
2013-01-29 20:11 ` Toralf Förster
2013-01-29 20:25 ` Jonathan Nieder [this message]
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=20130129202518.GE18266@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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).