git/builtin at c1b3c71f4b4571abb2b2a457122fd100dc9f7eb0 - git

History

Jeff King bc6b8fc130 use get_commit_buffer everywhere Each of these sites assumes that commit->buffer is valid. Since they would segfault if this was not the case, they are likely to be correct in practice. However, we can future-proof them by using get_commit_buffer. And as a side effect, we abstract away the final bare uses of commit->buffer. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>		11 years ago
..
add.c	…
annotate.c	…
apply.c	…
archive.c	…
bisect--helper.c	…
blame.c	…
branch.c	…
bundle.c	…
cat-file.c	…
check-attr.c	…
check-ignore.c	…
check-mailmap.c	…
check-ref-format.c	…
checkout-index.c	…
checkout.c	…
clean.c	…
clone.c	…
column.c	…
commit-tree.c	…
commit.c	…
config.c	…
count-objects.c	…
credential.c	…
describe.c	…
diff-files.c	…
diff-index.c	…
diff-tree.c	…
diff.c	…
fast-export.c	use get_commit_buffer everywhere	11 years ago
fetch-pack.c	…
fetch.c	…
fmt-merge-msg.c	use get_commit_buffer everywhere	11 years ago
for-each-ref.c	…
fsck.c	…
gc.c	…
get-tar-commit-id.c	…
grep.c	…
hash-object.c	…
help.c	…
index-pack.c	…
init-db.c	…
log.c	use get_commit_buffer everywhere	11 years ago
ls-files.c	…
ls-remote.c	…
ls-tree.c	…
mailinfo.c	…
mailsplit.c	…
merge-base.c	…
merge-file.c	…
merge-index.c	…
merge-ours.c	…
merge-recursive.c	…
merge-tree.c	…
merge.c	…
mktag.c	…
mktree.c	…
mv.c	…
name-rev.c	…
notes.c	…
pack-objects.c	…
pack-redundant.c	…
pack-refs.c	…
patch-id.c	…
prune-packed.c	…
prune.c	…
push.c	…
read-tree.c	…
receive-pack.c	…
reflog.c	…
remote-ext.c	…
remote-fd.c	…
remote.c	…
repack.c	…
replace.c	…
rerere.c	…
reset.c	…
rev-list.c	…
rev-parse.c	…
revert.c	…
rm.c	…
send-pack.c	…
shortlog.c	…
show-branch.c	…
show-ref.c	…
stripspace.c	…
symbolic-ref.c	…
tag.c	…
unpack-file.c	…
unpack-objects.c	…
update-index.c	…
update-ref.c	…
update-server-info.c	…
upload-archive.c	…
var.c	…
verify-pack.c	…
verify-tag.c	…
write-tree.c	…