Extracted from git v1.7.0 Release Notes: * "git push" into a branch that is currently checked out (i.e. pointed at by HEAD in a repository that is not bare) is refused by default. Update the user manual where necessary --- Documentation/user-manual.txt | 12 ++++++++---- 1 files changed, 8 insertions(+), 4 deletions(-) diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index fe6fb72..0897839 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -1963,10 +1963,14 @@ As with `git fetch`, `git push` will complain if this does not result in a handling this case. Note that the target of a "push" is normally a -<<def_bare_repository,bare>> repository. You can also push to a -repository that has a checked-out working tree, but the working tree -will not be updated by the push. This may lead to unexpected results if -the branch you push to is the currently checked-out branch! +<<def_bare_repository,bare>> repository. Until the version 1.7 you could +also push to a repository that has a checked-out working tree, +but the working tree will not be updated by the push. This might lead to +unexpected results if the branch you pushed to was the currently checked-out +branch! From 1.7.0 git push" into a branch that is currently checked out +(i.e. pointed at by HEAD in a repository that is not bare) +is refused by default. + As with `git fetch`, you may also set up configuration options to save typing; so, for example, after -- 1.6.6 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html