From: Jeff King <peff@peff.net>
To: "Rémy Hubscher" <hubscher.remy@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Improving the git remote command
Date: Tue, 26 Aug 2014 08:40:27 -0400 [thread overview]
Message-ID: <20140826124027.GE29180@peff.net> (raw)
In-Reply-To: <53FC537C.4080206@gmail.com>
On Tue, Aug 26, 2014 at 11:29:32AM +0200, Rémy Hubscher wrote:
> I'd like to add a list parameter to the `git remote` command.
>
> We already have:
>
> - `git remote add`
> - `git remote rename`
> - `git remote delete`
>
> I often write `git remote list` before finaly using `git remote -v` but
> it isn't intuitive.
Right now the list operation is done by giving no arguments at all. This
is a bit unlike other parts of git, which would usually define "git
remote list" and then say that if no command is given, "list" is the
default.
But...
> I am proposing to add `git remote list` as a shortcut for `git remote -v`
This is somewhat different. I would have expected "git remote list" to
do the same thing as "git remote" (i.e., list without "-v"). I guess it
does not have to, though.
Perhaps "-v" should have been the default all along. I do not use "git
remote" myself, so I don't know if "-v" is what most people use. But
changing the output of "git remote" now is probably a bad thing (I
expect some people may depend on parsing it to get the list of remotes;
they should probably use the git-config plumbing to do the same thing,
but it's actually rather tricky to do it that way).
-Peff
next prev parent reply other threads:[~2014-08-26 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 9:29 Improving the git remote command Rémy Hubscher
2014-08-26 10:05 ` Philippe Vaucher
2014-08-26 12:40 ` Jeff King [this message]
2014-08-26 16:19 ` Philippe Vaucher
2014-08-26 16:37 ` Jeff King
2014-08-26 17:24 ` Junio C Hamano
2014-08-26 17:33 ` Jeff King
2014-08-27 16:36 ` David Aguilar
2014-08-27 20:35 ` Junio C Hamano
2014-08-27 21:22 ` Keller, Jacob E
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=20140826124027.GE29180@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=hubscher.remy@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).