git 버전 업데이트 중 ... 이전 git 버전을 사용한 저장소에 대해 수행해야 할 작업이 있습니까?

아니에요. git1.7.x 버전과 2.0 버전 의 일상적인 사용의 유일한 차이점 은 다음과 같은 작업을 할 때 인쇄되는 메시지입니다 git push.

warning: push.default is unset; its implicit value has changed in Git
2.0 from 'matching' to 'simple'. To squelch this message and maintain the traditional behavior, use:

  git config --global push.default matching

To squelch this message and adopt the new behavior now, use:

  git config --global push.default simple

When push.default is set to 'matching', git will push local branches to the remote branches that already exist with the same name.

Since Git 2.0, Git defaults to the more conservative 'simple' behavior, which only pushes the current branch to the corresponding remote branch that 'git pull' uses to update the current branch.

See 'git help config' and search for 'push.default' for further information. (the 'simple' mode was introduced in Git 1.7.11. Use the similar mode 'current' instead of 'simple' if you sometimes use older versions of Git)

Counting objects: 15, done.
(...)

어쨌든, 특히 리포지토리를 관리하는 경우에는 업그레이드하기 전에 항상 릴리스 정보 를 읽는 것이 좋습니다 . 예를 들어, 위의 동작 은 릴리스 정보에 문서화되었습니다 .

When "git push [$there]" does not say what to push, we have used the
traditional "matching" semantics so far (all your branches were sent
to the remote as long as there already are branches of the same name
over there).  In Git 2.0, the default is now the "simple" semantics,
which pushes:

 - only the current branch to the branch with the same name, and only
   when the current branch is set to integrate with that remote
   branch, if you are pushing to the same remote as you fetch from; or

 - only the current branch to the branch with the same name, if you
   are pushing to a remote that is not where you usually fetch from.

You can use the configuration variable "push.default" to change
this.  If you are an old-timer who wants to keep using the
"matching" semantics, you can set the variable to "matching", for
example.  Read the documentation for other possibilities.