Dominique Quatravaux <domq@xxxxxxxxxx> writes:
> Instead of obtaining short SHA1's from "git rev-list" and hitting the repository
> once more with "git rev-parse" for the full-size SHA1's, obtain long SHA1's from
> "git rev-list" and truncate them with "cut".
That doesn't work if there are 7-digit SHA1 collisions in the repo.
Even my git.git has a bunch of them, as checked with
git rev-list --objects --all | cut -c1-7 | sort | uniq -d
and I expect a bigger project would have collisions beyond the 9th
digit.
What you can, however, do:
> -git rev-list $merges_option --pretty=oneline --abbrev-commit \
> - --abbrev=7 --reverse --left-right --topo-order \
> +git rev-list $merges_option --pretty=oneline --no-abbrev-commit \
> + --reverse --left-right --topo-order \
> $revisions | \
rev-list can give you *both* the abbreviated and full SHA1s if you say
git rev-list $merges_option --format="%>%h %H %s" <...etc...>
--
Thomas Rast
trast@{inf,student}.ethz.ch
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html