| commit | 1510dbe380a24fdf303a3c0594752cfdc968cb12 | |
| author | Matt McCutchen <matt@mattmccutchen.net> | |
| Mon, 24 Nov 2008 06:55:22 +0000 (24 01:55 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 28 Nov 2008 02:35:28 +0000 (27 18:35 -0800) | ||
| tree | d0bda0c0087f1e437917fdd6b0d5cb9e54bad226 | treesnapshot (tar.gz zip) |
| parent | c07838371b116251b6c4bc62a2ba64109baf74f1 | commitdiff |
git checkout: don't warn about unborn branch if -f is already passed
I think it's unnecessary to warn that the checkout has been forced due to an
unborn current branch if -f has been explicitly passed. For one project, I am
using git-new-workdir to create workdirs from a bare repository whose HEAD is
set to an unborn branch, and this warning started to irritate me.
Signed-off-by: Matt McCutchen <matt@mattmccutchen.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
I think it's unnecessary to warn that the checkout has been forced due to an
unborn current branch if -f has been explicitly passed. For one project, I am
using git-new-workdir to create workdirs from a bare repository whose HEAD is
set to an unborn branch, and this warning started to irritate me.
Signed-off-by: Matt McCutchen <matt@mattmccutchen.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin-checkout.c | diffblobblamehistory |