All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Marco Costalba <mcostalba@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Navigating remote branches in qgit
Date: Sun, 04 Feb 2007 22:13:55 -0500	[thread overview]
Message-ID: <1170645235.4191.26.camel@dv.roinet.com> (raw)
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:
> 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

  reply	other threads:[~2007-02-05  3:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-04  7:41 Navigating remote branches in qgit Pavel Roskin
2007-02-04  9:28 ` Marco Costalba
2007-02-04 11:00 ` Marco Costalba
2007-02-05  3:13   ` Pavel Roskin [this message]
2007-02-05 17:45     ` Marco Costalba
2007-02-07  8:31       ` Pavel Roskin

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=1170645235.4191.26.camel@dv.roinet.com \
    --to=proski@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=mcostalba@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.