aboutsummaryrefslogtreecommitdiff
path: root/git.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2007-12-03 00:03:10 -0800
committerJunio C Hamano <gitster@pobox.com>2007-12-03 00:45:21 -0800
commit5241b6bfe2285a6da598a0348c37b77964035bc8 (patch)
tree5d4f92a977193c8c5c1363a2c1f3b6dd0702d97f /git.c
parent9663c3bc6a04b9b4f63a54b820d3edb16aa95e6d (diff)
downloadgit-5241b6bfe2285a6da598a0348c37b77964035bc8.tar.gz
git-5241b6bfe2285a6da598a0348c37b77964035bc8.tar.xz
git-commit --allow-empty
It does not usually make sense to record a commit that has the exact same tree as its sole parent commit and that is why git-commit prevents you from making such a mistake, but when data from foreign scm is involved, it is a different story. We are equipped to represent such an (perhaps insane, perhaps by mistake, or perhaps done on purpose) empty change, and it is better to represent it bypassing the safety valve for native use. This is primarily for use by foreign scm interface scripts. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git.c')
0 files changed, 0 insertions, 0 deletions