From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Bryan Turner <bturner@atlassian.com>,
pedro rijo <pedrorijo91@gmail.com>,
Git Users <git@vger.kernel.org>
Subject: Re: Find main branch
Date: Fri, 15 Jan 2016 13:02:53 -0500 [thread overview]
Message-ID: <20160115180253.GA9590@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqq1t9ikaxb.fsf@gitster.mtv.corp.google.com>
On Fri, Jan 15, 2016 at 09:30:24AM -0800, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > It would be nice if "git ls-remote" just had some way of printing the
> > capabilities.
>
> I would agree that it would be nice to give an option to ls-remote
> to show which ones are symrefs pointing at what. You are being more
> ambitious than that, but I am not sure I would agree it is a good
> idea.
>
> Most normal capabilities have no value to ordinary end users, and
> the symref= thing is interesting for them only because there isn't
> such an option in ls-remote (hence "capabilities" thing could be
> used as a poor-man's substitute).
I thought it might be nice for any porcelain which tries to wrap
`ls-remote`, make some decision based on the capabilities, and then
invoke another plumbing command. But I guess that is probably slightly
crazy, and nobody is doing it.
Something like `ls-remote --symrefs` probably would be a better place to
start.
-Peff
next prev parent reply other threads:[~2016-01-15 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 18:17 Find main branch pedro rijo
2016-01-14 18:26 ` Stefan Beller
2016-01-14 18:31 ` Konstantin Khomoutov
2016-01-14 18:40 ` pedro rijo
2016-01-14 18:53 ` Konstantin Khomoutov
2016-01-14 19:12 ` Bryan Turner
2016-01-14 21:13 ` Jeff King
2016-01-15 10:49 ` pedro rijo
2016-01-15 17:30 ` Junio C Hamano
2016-01-15 18:02 ` Jeff King [this message]
2016-01-14 21: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=20160115180253.GA9590@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pedrorijo91@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).