From: "Santi Béjar" <santi@agolina.net>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Jay Soffian <jaysoffian@gmail.com>,
git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] builtin-branch: highlight current remote branches with an asterisk
Date: Tue, 10 Feb 2009 09:02:02 +0100 [thread overview]
Message-ID: <adf1fd3d0902100002k5d787e2ewe9012b42f943a6a3@mail.gmail.com> (raw)
In-Reply-To: <20090210075214.GC1320@atjola.homenet>
2009/2/10 Björn Steinbrink <B.Steinbrink@gmx.de>:
> On 2009.02.09 18:32:06 -0500, Jay Soffian wrote:
>> Teach git branch -{r,a} how to interpret remote HEADs and highlight the
>> corresponding remote branch with an asterisk, instead of showing literal
>> "<remote_name>/HEAD".
>
> Hm, what's the use case for having such a marker? And since only "git
> clone" sets up origin/HEAD, while "git remote add foo git://..." won't
> create foo/HEAD,
git remote add -f ... would create it.
> you would get that marker for origin only. Also, the
> origin/HEAD symref isn't updated, so it doesn't tell you which branch
> is "active" in the remote repository now, but which one was active when
> you cloned the repo.
Maybe there should be a way to update it afterwards.
Santi
next prev parent reply other threads:[~2009-02-10 8:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 23:32 [PATCH] builtin-branch: highlight current remote branches with an asterisk Jay Soffian
2009-02-09 23:49 ` Johannes Schindelin
2009-02-10 0:03 ` Mark Burton
2009-02-10 0:22 ` Jay Soffian
2009-02-10 11:05 ` Mark Burton
2009-02-10 0:24 ` Junio C Hamano
2009-02-10 7:59 ` Santi Béjar
2009-02-10 0:10 ` Jay Soffian
2009-02-10 7:52 ` Björn Steinbrink
2009-02-10 8:02 ` Santi Béjar [this message]
2009-02-10 8:24 ` Björn Steinbrink
2009-02-10 11:19 ` Jeff King
2009-02-10 11:50 ` Björn Steinbrink
2009-02-10 11:59 ` Jeff King
2009-02-10 12:23 ` Björn Steinbrink
2009-02-10 13:04 ` Jeff King
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=adf1fd3d0902100002k5d787e2ewe9012b42f943a6a3@mail.gmail.com \
--to=santi@agolina.net \
--cc=B.Steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@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).