summaryrefslogtreecommitdiff
path: root/git-filter-branch.sh
diff options
context:
space:
mode:
authorLibravatar Johan Herland <johan@herland.net>2011-03-30 02:02:55 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2011-03-30 13:13:52 -0700
commit84a7e35eea97388ba5ca458808119650818c2fd2 (patch)
tree718a121d0a748234fa3c79732733e73fd88185cb /git-filter-branch.sh
parentMerge branch 'maint' (diff)
downloadtgif-84a7e35eea97388ba5ca458808119650818c2fd2.tar.xz
Make "git notes add" more user-friendly when there are existing notes
Currently, "notes add" (without -f/--force) will abort when the given object already has existing notes. This makes sense for the modes of "git notes add" that would necessarily overwrite the old message (when using the -m/-F/-C/-c options). However, when no options are given (meaning the notes are created from scratch in the editor) it is not very user-friendly to abort on existing notes, and forcing the user to run "git notes edit". Instead, it is better to simply "redirect" to "git notes edit" automatically, i.e. open the existing notes in the editor and let the user edit them. This patch does just that. This changes the behavior of "git notes add" without options when notes already exist for the given object, but I doubt that many users really depend on the previous failure from "git notes add" in this case. Signed-off-by: Johan Herland <johan@herland.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-filter-branch.sh')
0 files changed, 0 insertions, 0 deletions