aboutsummaryrefslogtreecommitdiff
path: root/hash.c
diff options
context:
space:
mode:
authorMichael J Gruber <git@drmicha.warpmail.net>2011-08-25 12:26:37 +0200
committerJunio C Hamano <gitster@pobox.com>2011-08-25 13:16:46 -0700
commit11432bb467c2ba45014fc2fe8c4e23c92b7356d6 (patch)
treea1c764f4a3ae8ddd0f9a418cd7115d621ca6908f /hash.c
parentccef6048cd697063967e5e02937911fd8125b364 (diff)
downloadgit-11432bb467c2ba45014fc2fe8c4e23c92b7356d6.tar.gz
git-11432bb467c2ba45014fc2fe8c4e23c92b7356d6.tar.xz
git-notes.txt: clarify -C vs. copy and -F
The current description of '-C' together with the analogy to 'git commit -C' can lead to the wrong conclusion that '-C' copies notes between objects. Make this clearer by rewording and pointing to 'copy'. The example for attaching binary notes with 'git hash-object' followed by 'git notes add -C' immediately raises the question: "Why not use 'git notes add -F'?". Answer it (the latter is not binary-safe). Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net> Acked-by: Johan Herland <johan@herland.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'hash.c')
0 files changed, 0 insertions, 0 deletions