From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: "Roger C. Soares" <rogersoares@intelinet.com.br>,
"Shawn O. Pearce" <spearce@spearce.org>,
Dave Watson <dwatson@mimvista.com>
Cc: git@vger.kernel.org
Subject: Re: [EGIT PATCH] Branch bar in resource history.
Date: Mon, 10 Mar 2008 01:00:28 +0100 [thread overview]
Message-ID: <200803100100.28927.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <1204954828-3937-1-git-send-email-rogersoares@intelinet.com.br>
Den Saturday 08 March 2008 06.40.28 skrev Roger C. Soares:
> Adds a bar to show the current branch in resource history.
> Because other programs can change the current branch, the branch bar
> helps the user to remember what is being displayed in resource history.
> The bar can be disabled through a local menu preference.
Good idea, but I wonder if we wouldn't be better off trying too keep compact
and do this decoration in the first bar instead, either as an icon or just
text. I only have 15 inches of preciousss screen space. Compare to what you
did with the compare view in removing those unnecessary directory levels that
really only wasted space. That was very good.
Another idea would be to allow the user to filter which branches and I think
one could combine this indicator with that functionality through e.g. a poup
menu.
The green color on the indicator sugests something is "ok"?
-- robin
next prev parent reply other threads:[~2008-03-10 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 5:40 [EGIT PATCH] Branch bar in resource history Roger C. Soares
2008-03-10 0:00 ` Robin Rosenberg [this message]
2008-03-10 5:13 ` Roger Carneiro Soares
2008-03-10 23:14 ` Shawn O. Pearce
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=200803100100.28927.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=dwatson@mimvista.com \
--cc=git@vger.kernel.org \
--cc=rogersoares@intelinet.com.br \
--cc=spearce@spearce.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).