Re: Should revision hashes match between hosts for -current?

bob prohaska <fbsd@www.zefox.net> writes:
> Dag-Erling Smørgrav <des@freebsd.org> writes:
> > Run `git log --first-parent --oneline --no-decorate` in /usr/src on each
> > host and compare the output.
> Not sure what I'm looking for. The comments are recognizable, the matching
> hashes look clearly related but not the same, for example
>
> e7efe2f059a4 firewire: remove deprecation notice from manual page
> vs
> e7efe2f059a firewire: remove deprecation notice from manual page
>
> Now I'm wondering where the extra 4 came from....

The actual hash is e7efe2f059a474f8f8e14393713071761a633e65.  To make
log output easier to read, Git normally abbreviates hashes to a length
it assumes will be sufficient to ensure uniqueness, based on the number
of objects in the repository; if one of your trees was cloned with
--shallow or --single-branch, it will be much smaller than a full clone
and Git may pick a shorter length.

You can force Git to always use the same length by setting the
core.abbrev configuration variable:

    git config --global core.abbrev 12

Or you can add --abbrev=12 to the command I gave you.

DES
-- 
Dag-Erling Smørgrav - des@FreeBSD.org