Re: Improving the git remote command

2014-08-27 Thread Keller, Jacob E
On Wed, 2014-08-27 at 13:35 -0700, Junio C Hamano wrote: > David Aguilar writes: > > > We have some internal scripts at Disney Animation that rely on "git remote" > > output so I would vote for #3 personally as well. > > I take it that you mean you would vote _against_ #3 which will break > the

Re: Improving the git remote command

2014-08-27 Thread Junio C Hamano
David Aguilar writes: > We have some internal scripts at Disney Animation that rely on "git remote" > output so I would vote for #3 personally as well. I take it that you mean you would vote _against_ #3 which will break the expectation. > I know that "git config" is porcelain, and I can get re

Re: Improving the git remote command

2014-08-27 Thread David Aguilar
On Tue, Aug 26, 2014 at 01:33:12PM -0400, Jeff King wrote: > On Tue, Aug 26, 2014 at 10:24:35AM -0700, Junio C Hamano wrote: > > > Jeff King writes: > > > > > ... But we are left with three options: > > > > > > 1. Add "git remote list" with verbose output. This is bad because it > > > dif

Re: Improving the git remote command

2014-08-26 Thread Jeff King
On Tue, Aug 26, 2014 at 10:24:35AM -0700, Junio C Hamano wrote: > Jeff King writes: > > > ... But we are left with three options: > > > > 1. Add "git remote list" with verbose output. This is bad because it > > differs gratuitously from "git remote". > > > > 2. Add "git remote list" wit

Re: Improving the git remote command

2014-08-26 Thread Junio C Hamano
Jeff King writes: > ... But we are left with three options: > > 1. Add "git remote list" with verbose output. This is bad because it > differs gratuitously from "git remote". > > 2. Add "git remote list" with non-verbose output. This is good because > it means "git remote" is just a

Re: Improving the git remote command

2014-08-26 Thread Jeff King
On Tue, Aug 26, 2014 at 06:19:20PM +0200, Philippe Vaucher wrote: > > 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 s

Re: Improving the git remote command

2014-08-26 Thread Philippe Vaucher
> 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 shou

Re: Improving the git remote command

2014-08-26 Thread Jeff King
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`

Re: Improving the git remote command

2014-08-26 Thread Philippe Vaucher
> I often write `git remote list` before finaly using `git remote -v` but > it isn't intuitive. > > I am proposing to add `git remote list` as a shortcut for `git remote -v` I suffer from the same problem. I think your proposal is a logical and nice idea. Philippe -- To unsubscribe from this list

Improving the git remote command

2014-08-26 Thread Rémy Hubscher
Hi, 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. I am proposing to add `git remote list` as a shortcu