git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Navigating remote branches in qgit

From
PRPavel Roskin <proski@gnu.org>
Date
Feb 7, 2007, 08:31 UTC
Message-ID
<1170837104.11150.128.camel@dv>
In-Reply-To
<e5bfff550702050945l528b764apacc69b79c60dfb7a@mail.gmail.com>
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:
Show 5 quoted lines
> 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
Previous: Marco Costalba
Message 6 of 6 in “Navigating remote branches in qgit”
  1. Pavel RoskinFeb 4, 2007
  2. Marco CostalbaFeb 4, 2007
  3. Marco CostalbaFeb 4, 2007
  4. Pavel RoskinFeb 5, 2007
  5. Marco CostalbaFeb 5, 2007
  6. Pavel RoskinFeb 7, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.