Re: Should revision hashes match between hosts for -current?
Warner Losh <[email protected]> Fri, 24 Jul 2026 19:13:52 -0600
| Newsgroups | gmane.os.freebsd.current |
|---|---|
| Message-ID | <CANCZdfrBmCMZX7iZ1h4AMfQ24cWgejwD6oes4h4x8v5PWgpM1w@mail.gmail.com> |
--0000000000009c6bdf06576534de Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jul 24, 2026, 6:22=E2=80=AFPM bob prohaska <[email protected]> wro= te: > On Thu, Jul 23, 2026 at 07:56:11PM +0200, Dag-Erling Sm=C3=B8rgrav wrote: > > bob prohaska <[email protected]> writes: > > > Should revision hashes match between different hosts if updated at th= e > > > 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 eac= h > > host and compare the output. > > Not sure what I'm looking for. The comments are recognizable, the matchin= g > 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 > > > --0000000000009c6bdf06576534de Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div><br><br><div class=3D"gmail_quote gmail_quote_contai= ner"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jul 24, 2026, 6:22=E2=80= =AFPM bob prohaska <<a href=3D"mailto:[email protected]">[email protected]= .net</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar= gin: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=C3=B8rgrav wrote:<br> > bob prohaska <<a href=3D"mailto:[email protected]" target=3D"_blan= k" rel=3D"noreferrer">[email protected]</a>> writes:<br> > > Should revision hashes match between different hosts if updated a= t 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 ea= ch<br> > host and compare the output.<br> <br> Not sure what I'm looking for. The comments are recognizable, the match= ing<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=3D"auto"><br></div><div dir=3D"auto">Different versions of = git compute Different lengths of hash to print / include.</div><div dir=3D"= auto"><br></div><div dir=3D"auto">Warner=C2=A0</div><div dir=3D"auto"><br><= /div><div dir=3D"auto"><div class=3D"gmail_quote gmail_quote_container"><bl= ockquote class=3D"gmail_quote" style=3D"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> --0000000000009c6bdf06576534de--