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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
