News for hackers. Stuff that matters.
Re:Git 2.0 is here by izacus on Friday June 06, 2014 @08:24AM (#7857432)
Yeah, I was hoping for that too. Having totally inconsistent switches and parameters (How many different ways is to "list" something in git? -a -v -l depending on command?) depending on command drives me up the wall way more than in should :/
Re:Git 2.0 is here by sergiotapia on Friday June 06, 2014 @10:00AM (#7857879)
I always found the `git remote -v` command really weird.

Why `-v`?

Re:Git 2.0 is here by jaybuff on Friday June 06, 2014 @10:04AM (#7857908)
verbose?
Re:Git 2.0 is here by rch on Friday June 06, 2014 @10:42AM (#7858127)
correct. If you allow the bare command 'git remote' to do anything, it might as well give back the remote names list. If you want more detail, pass -v as usual.
Re:Git 2.0 is here by hughw on Friday June 06, 2014 @09:00AM (#7857595)
"A foolish consistency is the hobgoblin of little minds" -- Emerson
Re:Git 2.0 is here by sopooneo on Friday June 06, 2014 @09:04AM (#7857608)
Certainly. But command line consistency is not foolish.
Re:Git 2.0 is here by worklogin on Friday June 06, 2014 @10:05AM (#7857913)
Consistency isn't always foolish.
Re:Git 2.0 is here by cgag on Friday June 06, 2014 @02:59PM (#7859729)
Their choice to stay consistent with their initial terrible ui design is the type of foolish consistency this quote is probably referring to.
Re:Git 2.0 is here by _broody on Friday June 06, 2014 @12:39PM (#7858925)
Ah, was that not Larry Wall moments before inventing a language intended to parse bashing one's head against the keyboard?
Re:Git 2.0 is here by hughw on Monday June 09, 2014 @05:46PM (#7870705)
Downvotes demonstrating my point.