git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: git@vger.kernel.org
Subject: gitk doesn't always shows boths tags in "gitk tag1..tag2"
Date: Tue, 29 Jan 2013 20:40:34 +0100	[thread overview]
Message-ID: <510825B2.6070805@gmx.de> (raw)

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

             reply	other threads:[~2013-01-29 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 19:40 Toralf Förster [this message]
2013-01-29 19:57 ` gitk doesn't always shows boths tags in "gitk tag1..tag2" Jonathan Nieder
2013-01-29 20:11   ` Toralf Förster
2013-01-29 20:25     ` Jonathan Nieder

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=510825B2.6070805@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=git@vger.kernel.org \
    /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).