git.vger.kernel.org archive mirror
 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: Wed, 07 Feb 2007 03:31:44 -0500	[thread overview]
Message-ID: <1170837104.11150.128.camel@dv> (raw)
In-Reply-To: <e5bfff550702050945l528b764apacc69b79c60dfb7a@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]

Hello, Marco!

Thank you for all your fixes!  You have greatly improved usability of
qgit for me.

On Mon, 2007-02-05 at 18:45 +0100, Marco Costalba wrote:

> 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.

Well, the only example with multiple remotes is my Linux repository, and
I'm afraid it would be too large.  So I'm attaching compressed output of
git-show-refs.

Actually, I'm not sure if multiple remotes is such a common case to add
a level in menu hierarchy just to support them.

My feeling is that the popup menu is already heavily overloaded, and
some things just need to be accessed from specialized dialogs.

I think some design decisions should come from git.  What are we going
to do if there are thousands of tags and branches?  How are we going to
sort them in git?

-- 
Regards,
Pavel Roskin

[-- Attachment #2: showref.bz2 --]
[-- Type: application/x-bzip, Size: 3876 bytes --]

      reply	other threads:[~2007-02-07  8:32 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
2007-02-07  8:31       ` Pavel Roskin [this message]

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=1170837104.11150.128.camel@dv \
    --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 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).