From: Santi Béjar <santi@agolina.net>
Date: Tue, 04 Aug 2009 09:44:31 GMT
Subject: Re: [PATCH] gitk: new option to hide remote refs
Message-ID: <adf1fd3d0908040244m1c7d45ffw67be74091da74730@mail.gmail.com>
In-Reply-To: <200908041108.19108.trast@student.ethz.ch>

2009/8/4 Thomas Rast <trast@student.ethz.ch>:
> Junio C Hamano wrote:
>> Thomas Rast <trast@student.ethz.ch> writes:
>>
>> > -       if {![string match "*/HEAD" $name]} {
>> > +       if {![string match "*/HEAD" $name] && !$hideremotes} {
>>
>> Hmm, I wonder if it would be more useful to extend this by using $skiprefs
>> pattern instead, like so:
> [...]
>> +     if {$skiprefs != "" && [string match $skiprefs $name]} continue
>
> Shortly after sending the patch, I had another idea: how about an
> option to only show refs that were given on the command line, if any?
> That way 'gitk --branches' or 'gitk HEAD' would hide the whole remotes
> mess (and of course also all other refs in the process).  I think I
> might be able to voodoo enough Tk to implement this.

Another possibility could be to have just an indication that the
commit has branches and/or tags pointing to it. Maybe just as it is
now but without the branch/tag name.

To mimic the current UI it could be:

o-<|-|_| Commit summary

with:

 o the current circle
 <| a yellow triangle
 |_| a green square

and then if you click on them you could get the current view, or a
list of branches/tags in the lower panel.

my 2 cents,
Santi