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 12:00:11 +0100 [thread overview]
Message-ID: <e5bfff550702040300x60bb1dfdxd312dc214bc49014@mail.gmail.com> (raw)
In-Reply-To: <1170574889.21644.38.camel@dv>
On 2/4/07, Pavel Roskin <proski@gnu.org> wrote:
> Hello, Marco!
>
> While at that, we should think how to show refs in a more compact manner
> in the revision list. I think "refs/" can be dropped in any case, since
> qgit only scans under refs. Any rectangle implies "refs/" already.
> That's what gitk does.
>
After the posted two patches "refs/" is shown only in StGIT bases. Currently
qgit uses 'git show-ref -d' to retrieve ref list and "ref/" prefix is
already in git-show-ref output,
so as a general rule I would try to avoid 'massaging' git output as
much as is possible to have more chances thing do not break after a
git behaviour change.
It is difficult now to say it's (and will be) true that refs are only
under "refs/". Perhaps in the future someone came up with an idea to
use "refs_of_some_kind/" directory and this would break stuff.
So last line is: if git-show-ref prints this info, perhaps it's better to keep.
Marco
next prev parent reply other threads:[~2007-02-04 11:00 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 [this message]
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=e5bfff550702040300x60bb1dfdxd312dc214bc49014@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).