Date: Fri, 24 Jul 2026 19:13:52 -0600 From: Warner Losh <imp@bsdimp.com> To: bob prohaska <fbsd@www.zefox.net> Cc: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= <des@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Should revision hashes match between hosts for -current? Message-ID: <CANCZdfrBmCMZX7iZ1h4AMfQ24cWgejwD6oes4h4x8v5PWgpM1w@mail.gmail.com> In-Reply-To: <amQB4Ei53gGxpaKl@www.zefox.net> References: <amI8nymlOLyagvUL@www.zefox.net> <86ik65wpxg.fsf@ltc.des.dev> <amQB4Ei53gGxpaKl@www.zefox.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Fri, Jul 24, 2026, 6:22 PM bob prohaska <fbsd@www.zefox.net> wrote: > On Thu, Jul 23, 2026 at 07:56:11PM +0200, Dag-Erling Smørgrav wrote: > > bob prohaska <fbsd@www.zefox.net> writes: > > > Should revision hashes match between different hosts if updated at the > > > same time? > > > > No, they should match if they were built from the same point in Git > > history (same revision of same branch). > > > > Ok, the systems were set up at different time and have been "git reset" > more than once, at different times. Sounds like nothing's wrong. > > > > > 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.... > Different versions of git compute Different lengths of hash to print / include. Warner 8-) > > Thanks for writing, > > bob prohaska > > > [-- Attachment #2 --] <div dir="auto"><div><br><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Jul 24, 2026, 6:22 PM bob prohaska <<a href="mailto:fbsd@www.zefox.net">fbsd@www.zefox.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Jul 23, 2026 at 07:56:11PM +0200, Dag-Erling Smørgrav wrote:<br> > bob prohaska <<a href="mailto:fbsd@www.zefox.net" target="_blank" rel="noreferrer">fbsd@www.zefox.net</a>> writes:<br> > > Should revision hashes match between different hosts if updated at the<br> > > same time?<br> > <br> > No, they should match if they were built from the same point in Git<br> > history (same revision of same branch).<br> > <br> <br> Ok, the systems were set up at different time and have been "git reset"<br> more than once, at different times. Sounds like nothing's wrong.<br> <br> > <br> > Run `git log --first-parent --oneline --no-decorate` in /usr/src on each<br> > host and compare the output.<br> <br> Not sure what I'm looking for. The comments are recognizable, the matching<br> hashes look clearly related but not the same, for example<br> <br> e7efe2f059a4 firewire: remove deprecation notice from manual page<br> vs<br> e7efe2f059a firewire: remove deprecation notice from manual page<br> <br> Now I'm wondering where the extra 4 came from....<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Different versions of git compute Different lengths of hash to print / include.</div><div dir="auto"><br></div><div dir="auto">Warner </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> 8-)<br> <br> Thanks for writing,<br> <br> bob prohaska<br> <br> <br> </blockquote></div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrBmCMZX7iZ1h4AMfQ24cWgejwD6oes4h4x8v5PWgpM1w>