git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: gitweb "tag" display
Date: Sat, 20 Aug 2005 09:21:39 +1000	[thread overview]
Message-ID: <17158.27011.7426.577686@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <7vpssq7vfa.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano writes:

> If you can pop-up a temporary window that shows the tag contents
> when I hover over a tag icon for 2 seconds, and remove that
> temporary window when step outside it would be ideal.  It is up

I did something a little easier - if you click on the tag, it now
displays the contents of the tag in the details pane.  Is that good
enough?

> to you to implement the part to show my wife's picture, reading
> "object-content-type: image/jpeg" thing ;-).  That one was not a
> serious request.

Well, Tk can display inline images in text widgets... :)

> I have two more requests to gitk, which are related to each
> other but not related to the "tag contents" one above:
> 
>  - if "gitk --all" slurped not just refs/heads and refs/tags but
>    everything under refs/* recursively, that would help
>    visualizing the bisect status.  bisect creates bunch of
>    commit object names in refs/bisect.
> 
>  - I have not looked at the code closely enough, but I cannot
>    find how to re-read references.  I would appreciate it if it
>    allowed it.  This relates to the bisect status visualization,
>    where the set of references changes _after_ the user started
>    gitk.

I implemented these two.  There is now a "Reread references" button in
the File menu.  References other than tags and heads get displayed in
a light blue box.

Hmmm... now I suppose we want a way to use gitk to drive the git
bisection process... :)

Paul.

  reply	other threads:[~2005-08-19 23:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-30  1:51 Display of merges in gitk Paul Mackerras
2005-07-30  4:25 ` Junio C Hamano
2005-07-30 21:36   ` Shipping gitk as part of core git Junio C Hamano
2005-07-31 12:00     ` Paul Mackerras
2005-07-31 18:48       ` Junio C Hamano
2005-07-30 14:32 ` gitk merge display bugs (was: Re: Display of merges in gitk) Sergey Vlasov
2005-08-05 14:10 ` Display of merges in gitk Linus Torvalds
2005-08-05 14:37   ` gitk "hyperlinks" (was Re: Display of merges in gitk) Linus Torvalds
2005-08-05 18:51     ` jepler
2005-08-06  3:36     ` Kay Sievers
2005-08-06 15:44       ` Linus Torvalds
2005-08-07  5:51         ` Kay Sievers
2005-08-06 18:27       ` gitweb "tag" display Junio C Hamano
2005-08-06 18:49         ` Junio C Hamano
2005-08-19 23:21           ` Paul Mackerras [this message]
2005-08-19 23:43             ` Johannes Schindelin
2005-08-20 19:09             ` Junio C Hamano
2005-08-07  5:50         ` Kay Sievers
2005-08-06 13:16     ` gitk "hyperlinks" (was Re: Display of merges in gitk) Paul Mackerras
2005-08-06 16:20       ` Linus Torvalds
2005-08-06 17:07         ` jepler
2005-08-06 17:59         ` gitk SHA link hovers Linus Torvalds
2005-08-07 12:04           ` Paul Mackerras
2005-08-06 16:31       ` gitk "hyperlinks" Junio C Hamano
2005-08-07 12:05         ` Paul Mackerras

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=17158.27011.7426.577686@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).