From: Marc Branchaud <mbranchaud@xiplink.com>
To: Paul Mackerras <paulus@samba.org>,
Nicolas Cornu <ncornu@aldebaran-robotics.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] gitk: Add a horizontal scrollbar for commit history
Date: Mon, 04 Nov 2013 10:50:04 -0500 [thread overview]
Message-ID: <5277C22C.8050605@xiplink.com> (raw)
In-Reply-To: <20131031090526.GA9164@iris.ozlabs.ibm.com>
On 13-10-31 05:05 AM, Paul Mackerras wrote:
> On Wed, Oct 30, 2013 at 01:47:08PM +0100, Nicolas Cornu wrote:
>> This is useful on all our repos, every times, as we put a tag per day.
>> If the HEAD didn't move during 150 days, we got 150 tags.
>
> Here is a patch that I did some time ago but have never pushed out.
> Do you think it is an improvement when using gitk on a repo with lots
> of tags?
I like this a lot! Thanks for putting it together. I think it's worth
releasing this as-is.
My only wish is that it be generalized for any kind of ref: Each refs/*
namespace should form a distinct display category. For example, given refs
like this (note the non-standard "builds" namespace):
refs/heads/maint
refs/heads/master
refs/heads/next
refs/remotes/origin/maint
refs/remotes/origin/master
refs/remotes/origin/next
refs/remotes/origin/pu
refs/tags/v1.1.1
refs/tags/v2.2.2
refs/tags/v3.3.3
refs/tags/v4.4.4
refs/builds/1.1.1-1
refs/builds/1.1.1-2
refs/builds/1.1.1-3
refs/builds/1.1.1-4
refs/builds/1.1.1-5
And let's say that somehow all these refs refer to the same commit that's
being displayed in gitk, then I'd like to see something like:
[3 branches...][4 remote refs...][4 tags...][5 builds...]
Gitk can be smart about how it displays standard namespaces (as it already is
for tags, heads, remote heads, etc.), but for non-standard namespaces gitk
can just display the namespace's name directly.
M.
prev parent reply other threads:[~2013-11-04 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 10:58 [PATCH v2] gitk: Add a horizontal scrollbar for commit history Nicolas Cornu
2013-10-30 12:01 ` Johannes Sixt
2013-10-30 12:47 ` Nicolas Cornu
2013-10-30 14:46 ` Marc Branchaud
2013-10-30 14:49 ` Nicolas Cornu
2013-10-30 15:04 ` Marc Branchaud
2013-10-31 9:05 ` Paul Mackerras
2013-11-02 9:40 ` Heiko Voigt
2013-11-04 15:50 ` Marc Branchaud [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=5277C22C.8050605@xiplink.com \
--to=mbranchaud@xiplink.com \
--cc=git@vger.kernel.org \
--cc=marcnarc@xiplink.com \
--cc=ncornu@aldebaran-robotics.com \
--cc=paulus@samba.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).