git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Sun, 4 Feb 2007 10:28:19 +0100	[thread overview]
Message-ID: <e5bfff550702040128o6283b4f3m91debc45ec6b151@mail.gmail.com> (raw)
In-Reply-To: <1170574889.21644.38.camel@dv>

Hello Pavel,

>
> Remote refs should recognized and be shown in a new color.  gitk uses
> orange (#ffddaa) on the left and green on the right.  I think qgit
> should use orange for the whole rectangle and drop "remotes/" in
> addition to "refs/", since the color will imply it.
>

I will post a quick patch, just to get the idea.

>
> It would be nice to have a refs browser that would show both loaded and
> non-loaded refs, but I realize that it's not a quick fix type of change.
>

Well, perhaps is not so hard, we already have

Git::getAllRefNames(uint mask, bool onlyLoaded)

that seems to fit. First parameter 'mask' could have following or-ed flags:

	enum RefType {
		TAG        = 1,
		BRANCH     = 2,
		RMT_BRANCH = 4,
		CUR_BRANCH = 8,
		REF        = 16,
		APPLIED    = 32,
		UN_APPLIED = 64,
		ANY_REF    = 127
	};


> Please feel free to ask for help with testing and design of the
> weirdness indicator :)
>

It should be great :-)

Marco

P.S: Grouped menu items patch will follow :-)

  reply	other threads:[~2007-02-04  9:28 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 [this message]
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

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=e5bfff550702040128o6283b4f3m91debc45ec6b151@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).