From: "Marco Costalba" <mcostalba@gmail.com>
To: "Pavel Roskin" <proski@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: Navigating remote branches in qgit
Date: Mon, 5 Feb 2007 18:45:28 +0100 [thread overview]
Message-ID: <e5bfff550702050945l528b764apacc69b79c60dfb7a@mail.gmail.com> (raw)
In-Reply-To: <1170645235.4191.26.camel@dv.roinet.com>
Hello Pavel,
> OK, I understand. I feel quite ambivalent on this if we stop showing
> StGIT bases. They seem internal details of StGIT to me.
>
Probably you are right. Patch pushed.
>
> I've made a patch that makes qgit use the same color as gitk. It looks
> much better to my eyes.
>
Thanks, applied.
> 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.
>
In your interesting test case at http://www.red-bean.com/proski/qgit/
all the remotes are on "origin", so in that case I don't see how
things could go better. Or perhaps I don't have understand the
grouping logic. In this case please give me some example based on your
repo, so I can understand the algorithm to use.
> 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/
>
Thanks. Fixed and patch pushed.
Marco
next prev parent reply other threads:[~2007-02-05 17:45 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
2007-02-05 17:45 ` Marco Costalba [this message]
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=e5bfff550702050945l528b764apacc69b79c60dfb7a@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=proski@gnu.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).