Pavel Roskin [off-list ref] writes:
git-patch-id is only used by git-cherry. git-cherry writes the second
SHA1 to some files in a temporary directory, but it never reads those
files, it only checks that they exist.
I do not oppose dropping the commit-id line from the default
output, but having it optionally available would be useful in
one application. Somebody _could_ write a tool that does
something like:
git-rev-list ^$old_head $new_head |
git-diff-tree -p -m --stdin --with-commit-ids |
git-patch-id
to cache the patch-id --> commit-id mappings. If this were kept
on the upstream repo for public query, it would be useful for
you to find out if your favorite patch as already been merged.
For example, gitweb could have an query page to let you submit a
patch-id and return the commit (or "no such patch merged yet").