![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Junio C Hamano <junkio@cox.net> | |
| Fri, 29 Dec 2006 00:32:17 +0000 (16:32 -0800) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Fri, 29 Dec 2006 02:37:33 +0000 (18:37 -0800) | ||
| commit | 013672bc589da395fcba9bf62d699e70f3764689 | |
| tree | 1a975ac6117cbe6bba07de4c4ff2312184dc8e01 | tree | snapshot |
| parent | e19b9ddab3fb7bd3bf6ed6629d3f014722e57a31 | commit | diff |
Allow non-fast-forward of remote tracking branches in default clone
This changes the default remote.origin.fetch configuration
created by git-clone so that it allows non-fast-forward updates.
When using the separate-remote layout with reflog enabled, it
does not make much sense to refuse to update the remote tracking
branch just because some of them do not fast-forward. git-fetch
issues warnings on non-fast-forwardness, and the user can peek
at what the previous state was using the reflog.
Signed-off-by: Junio C Hamano <junkio@cox.net>
This changes the default remote.origin.fetch configuration
created by git-clone so that it allows non-fast-forward updates.
When using the separate-remote layout with reflog enabled, it
does not make much sense to refuse to update the remote tracking
branch just because some of them do not fast-forward. git-fetch
issues warnings on non-fast-forwardness, and the user can peek
at what the previous state was using the reflog.
Signed-off-by: Junio C Hamano <junkio@cox.net>
| git-clone.sh | diff | blob | history |