git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: git-gui 0.7.3
Date: Mon, 11 Jun 2007 02:26:21 -0400	[thread overview]
Message-ID: <20070611062621.GE6073@spearce.org> (raw)

Linus recently pointed out that the blame viewer in git-gui 0.7.2
is useless, and the one parked seemingly indefinately in my pu
branch was much better, and couldn't do any worse than 0.7.2's.  

So here's git-gui 0.7.3, available in my maint branch:

  git://repo.or.cz/git-gui.git maint

for merging into the next public Git release.


Features since 0.7.2:

* New selection indication and softer colors.  This change is
  due to the efforts of Matthijs Melchior, and makes the main
  interface window slightly more pleasing to read.

* Vastly improved internal blame viewer.  The new viewer was
  incrementally improved, but in the end it amounted to a total
  rewrite by the time we reached the 0.7.3 release.

* Blame viewer now shows two blame passes side-by-side on the
  same file, giving the user fast access to original author and
  relocation author, for any line of the file.

* Mouse tooltips appear in the blame viewer when you mouse over
  a line of interest.

* Hyperlinks to original location are offered for both the original
  commit and the relocation commit in the blame viewer.

Bug fixes since 0.7.2:

* Allow creating a branch when none exists.  Previously we crashed
  if the repository had no local branches, but had a valid HEAD.

* Better handle internal Tk destroy messages sent to widgets;
  we used to terminate the entire git-gui process when any widget
  was destroyed.

* Minor font corrections, where git-gui was not honoring the user's
  configured preferences.

-- 
Shawn.

                 reply	other threads:[~2007-06-11  6:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070611062621.GE6073@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=torvalds@linux-foundation.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).