From: Junio C Hamano <gitster@pobox.com>
To: Ben Boeckel <mathstuf@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] add ls-remote --get-push-url option
Date: Fri, 31 Jul 2015 11:40:12 -0700 [thread overview]
Message-ID: <xmqqfv445fxv.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1438364321-14646-1-git-send-email-mathstuf@gmail.com> (Ben Boeckel's message of "Fri, 31 Jul 2015 13:38:40 -0400")
Ben Boeckel <mathstuf@gmail.com> writes:
> Not sure if it would be better to make a new variable or to reuse the existing
> one. I'm reusing it currently because it makes it easier to ensure they
> are mutually exclusive.
>
> Please keep me CC'd to the list; I'm not subscribed.
>
> Thanks,
>
> --Ben
>
> Ben Boeckel (1):
> ls-remote: add --get-push-url option
>
> Documentation/git-ls-remote.txt | 7 ++++++-
> builtin/ls-remote.c | 15 +++++++++++++--
> 2 files changed, 19 insertions(+), 3 deletions(-)
Probably get-url makes (some) sense because ls-remote is a "fetch
that does not actually fetch anything". But "get-push-url" to
ls-remote makes _no_ sense whatsoever. ls-remote and fetch do not
have to know or care about push-url; they do not even have to know
there exists a thing called "git push" ;-)
Wouldn't "git push -v -n" or something suit your needs already?
next prev parent reply other threads:[~2015-07-31 18:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 17:38 [PATCH] add ls-remote --get-push-url option Ben Boeckel
2015-07-31 17:38 ` [PATCH] ls-remote: add " Ben Boeckel
2015-07-31 18:40 ` Junio C Hamano [this message]
2015-07-31 18:56 ` [PATCH] add ls-remote " Ben Boeckel
2015-07-31 19:02 ` Junio C Hamano
2015-07-31 19:04 ` Ben Boeckel
2015-07-31 19:16 ` Junio C Hamano
2015-07-31 20:51 ` Ben Boeckel
2015-08-03 21:00 ` [PATCH v2] add git-url subcommand Ben Boeckel
2015-08-03 21:00 ` [PATCH v2] remote: add get-url subcommand Ben Boeckel
2015-08-03 23:38 ` Eric Sunshine
2015-08-04 0:16 ` Ben Boeckel
2015-08-04 0:45 ` Eric Sunshine
2015-08-04 14:56 ` [PATCH v3] " Ben Boeckel
2015-08-05 20:34 ` Junio C Hamano
2015-08-05 21:33 ` Ben Boeckel
2015-08-05 21:39 ` Junio C Hamano
2015-09-04 14:30 ` [PATCH v4] " Ben Boeckel
2015-09-04 22:40 ` Junio C Hamano
2015-09-16 1:53 ` [PATCH v5] " Ben Boeckel
2015-09-16 22:51 ` Junio C Hamano
2015-09-17 0:19 ` [PATCH v6] " Ben Boeckel
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=xmqqfv445fxv.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mathstuf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.