Re: Navigating remote branches in qgit

From: Pavel Roskin <proski@gnu.org>
Date: Feb 5, 2007, 03:13 UTC
Message-ID: <1170645235.4191.26.camel@dv.roinet.com>
In-Reply-To: <e5bfff550702040300x60bb1dfdxd312dc214bc49014@mail.gmail.com>

Hello, Marco!

Many many thanks for being such a great magician and granting my wishes so quickly :)

On Sun, 2007-02-04 at 12:00 +0100, Marco Costalba wrote:

Show 6 quoted lines

> After the posted two patches "refs/" is shown only in StGIT bases. Currently
> qgit uses 'git show-ref -d' to retrieve ref list and "ref/" prefix is
> already in git-show-ref output,
> so as a general rule I would try to avoid 'massaging' git output as
> much as is possible to have more chances thing do not break after a
> git behaviour change.

OK, I understand. I feel quite ambivalent on this if we stop showing StGIT bases. They seem internal details of StGIT to me.

Generally, if qgit shows unrecognized refs, it's a sign that it needs to be taught about them. So indeed, massaging things we don't fully understand would be bad.

Thanks for making the remote branches appear in a unique way, but I think you used a darker color than gitk, so they seem even more noticeable than the local branches.

I've made a patch that makes qgit use the same color as gitk. It looks much better to my eyes.

I think the popup menu for remote branches should have one more level of hierarchy. The branches should be grouped by remotes:

Remote branches -> wireless-2.6 -> master
                                   upstream
                   wireless-dev -> master
                                   for-linus

It may not be as quick to access, but jumping the branches is not going to happen often. It's more important to provide a good visualization.

Also, qgit seems to be confused on one of my repositories. It doesn't show any tags in the main menu and shows tags with branches under "More". I guess there are too many remote branches. The tarball is in http://www.red-bean.com/proski/qgit/

-- 
Regards,
Pavel Roskin