From: Paul Mackerras <paulus@samba.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Please pull gitk update
Date: Tue, 27 Mar 2012 20:52:05 +1100 [thread overview]
Message-ID: <20120327095204.GA8718@bloggs.ozlabs.ibm.com> (raw)
In-Reply-To: <7vsjgvkl69.fsf@alter.siamese.dyndns.org>
On Mon, Mar 26, 2012 at 04:16:30PM -0700, Junio C Hamano wrote:
> Here is what I came up with after looking at the result of this pull.
> Could you eyeball it?
>
> Thanks.
>
> diff --git a/Documentation/RelNotes/1.7.10.txt b/Documentation/RelNotes/1.7.10.txt
> index 11b0b10..e1f493c 100644
> --- a/Documentation/RelNotes/1.7.10.txt
> +++ b/Documentation/RelNotes/1.7.10.txt
> @@ -46,6 +46,14 @@ Updates since v1.7.9
> UI, Workflows & Features
>
> * various "gitk" updates.
> + - show the path to the top level directory in the window title
> + - update preference edit dialog
> + - pathspecs like "gitk -- .", "gitk -- ..\t" did not work well
This sounds a bit awkward, how about:
+ - display file list correctly when directories are given on command line
or something like that?
> + - make "git-describe" output in the log message into a clickable link
> + - avoid matching the UNIX timestamp part when searching all fields
> + - give preference to symboic font names like sans & monospace
> + - allow comparing two commits using a mark
> + - "gitk" honors log.showroot configuration.
>
> * Teams for localizing the messages from the Porcelain layer of
> commands are starting to form, thanks to Jiang Xin who volunteered
Other than that, looks fine.
Paul.
next prev parent reply other threads:[~2012-03-27 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 5:55 Please pull gitk update Paul Mackerras
2012-03-24 8:32 ` Junio C Hamano
2012-03-26 23:16 ` Junio C Hamano
2012-03-27 9:52 ` Paul Mackerras [this message]
2012-03-27 14:50 ` Zbigniew Jędrzejewski-Szmek
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=20120327095204.GA8718@bloggs.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).