From: Tay Ray Chuan <rctay89@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: [PATCH] ls-remote: default to 'origin' when no remote specified
Date: Thu, 8 Apr 2010 13:58:03 +0800 [thread overview]
Message-ID: <o2qbe6fef0d1004072258h3cab0156o9f63d6bfa732eb87@mail.gmail.com> (raw)
In-Reply-To: <7vochu8rg7.fsf@alter.siamese.dyndns.org>
Hi,
On Thu, Apr 8, 2010 at 1:05 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Tay Ray Chuan <rctay89@gmail.com> writes:
>
>> Instead of breaking execution when no remote (as specified in the
>> variable dest) is specified when git-ls-remote is invoked, continue on
>> and let remote_get() handle it.
>
> Shouldn't it default to "branch.$current.remote", not "origin", though, as
> ls-remote to inspect is most closely related to "git pull"?
actually, it already does so (remote_get() does all the magic); it was
my commit message that was not accurate.
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2010-04-08 5:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 3:58 [PATCH] ls-remote: default to 'origin' when no remote specified Tay Ray Chuan
2010-04-08 4:45 ` Jeff King
2010-04-08 5:35 ` Junio C Hamano
2010-04-08 6:25 ` Jeff King
2010-04-08 6:07 ` Tay Ray Chuan
2010-04-08 6:34 ` Jeff King
2010-04-08 6:44 ` Junio C Hamano
2010-04-08 6:47 ` Jeff King
2010-04-08 5:05 ` Junio C Hamano
2010-04-08 5:58 ` Tay Ray Chuan [this message]
2010-04-08 7:05 ` [PATCH v2] ls-remote: fall-back to default remotes " Tay Ray Chuan
2010-04-08 7:07 ` [PATCH v2 (resend)] " Tay Ray Chuan
2010-04-08 7:16 ` Jeff King
2010-04-08 17:10 ` Tay Ray Chuan
2010-04-08 17:21 ` [PATCH v3] " Tay Ray Chuan
2010-04-08 19:19 ` Jeff King
2010-04-09 8:49 ` Peter Kjellerstedt
2010-04-09 9:15 ` Tay Ray Chuan
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=o2qbe6fef0d1004072258h3cab0156o9f63d6bfa732eb87@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).