For many git commands, '-f/--force' is a way to force actions which would otherwise error out. Way more than once, I've been trying this with 'git branch -d' and 'git branch -m'...
I've had these two patches sitting in my tree for 3 years now it seems. Here's a rebase. In v2 I rename force_create to force and spell out the "-f" behaviour for other options in the commit message. Michael J Gruber (2): t3200-branch: test -M branch: allow -f with -m and -d builtin/branch.c | 13 +++++++++---- t/t3200-branch.sh | 14 ++++++++++++++ 2 files changed, 23 insertions(+), 4 deletions(-) -- 2.2.0.345.g7041aac -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
