0

In interactive, the update command just lists the commands again:

$ git add -i
           staged     unstaged path
  1:        +0/-3      nothing .bowerrc
  2:        +4/-1      nothing .meteor/packages

*** Commands ***
  1: status   2: update   3: revert   4: add untracked
  5: patch    6: diff     7: quit     8: help
What now> u
*** Commands ***
  1: status   2: update   3: revert   4: add untracked
  5: patch    6: diff     7: quit     8: help
What now> 2
*** Commands ***
  1: status   2: update   3: revert   4: add untracked
  5: patch    6: diff     7: quit     8: help
What now> update
*** Commands ***
  1: status   2: update   3: revert   4: add untracked
  5: patch    6: diff     7: quit     8: help
What now>

git version 2.2.1

According to

http://git-scm.com/book/en/v2/Git-Tools-Interactive-Staging

I should expect:

           staged     unstaged path
  1:    unchanged        +0/-1 TODO
  2:    unchanged        +1/-1 index.html
  3:    unchanged        +5/-1 lib/simplegit.rb
Update>>
Loren
  • 13,903
  • 8
  • 48
  • 79

2 Answers2

1

You are missing an important "state" that your repo must be in for the update command to do anything. From the doc examples, you can see:

$ git add -i
           staged     unstaged path
  1:    unchanged        +0/-1 TODO
  2:    unchanged        +1/-1 index.html
  3:    unchanged        +5/-1 lib/simplegit.rb

*** Commands ***
  1: status     2: update      3: revert     4: add untracked
  5: patch      6: diff        7: quit       8: help
What now>

However your state is:

$ ga -i
           staged     unstaged path
  1:        +0/-3      nothing .bowerrc
  2:        +4/-1      nothing .meteor/packages

The difference is in your staged/unstaged columns. The update command is purposed for staging new changes. Since you have nothing unstaged, the update command completes with no prompt.

sjagr
  • 15,983
  • 5
  • 40
  • 67
0

All changes had already been staged. Once I unstaged with git reset, it worked correctly.

Loren
  • 13,903
  • 8
  • 48
  • 79