summaryrefslogtreecommitdiff
path: root/git-revert.sh
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2007-01-19 19:51:29 (GMT)
committerJunio C Hamano <junkio@cox.net>2007-02-03 20:54:49 (GMT)
commit5f856dd47dacb30fb9f605b4b7e1fa577ada7d26 (patch)
tree634604cc8d2cb12588ea85be851a8581d89c59a2 /git-revert.sh
parent505739f6c0c67b7426ffbc723734c794b0a810d9 (diff)
downloadgit-5f856dd47dacb30fb9f605b4b7e1fa577ada7d26.zip
git-5f856dd47dacb30fb9f605b4b7e1fa577ada7d26.tar.gz
git-5f856dd47dacb30fb9f605b4b7e1fa577ada7d26.tar.bz2
fix reflog entries for "git-branch"
Even when -l is not given from the command line, the repository may have the configuration variable core.logallrefupdates set, or an old-timer might have done ": >.git/logs/refs/heads/new" before running "git branch new". In these cases, the code gave an uninitialized msg[] from the stack to be written out as the reflog message. This also passes a different message when '-f' option is used. Saying "git branch -f branch some-commit" is a moral equilvalent of doing "git-reset some-commit" while on the branch. Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'git-revert.sh')
0 files changed, 0 insertions, 0 deletions