Date: Sat, 18 Feb 2023 15:05:42 +0000 From: void <void@f-m.fm> To: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-23:02.openssh Message-ID: <d5105588-22f8-49c8-a236-bdc1af8b58fc@app.fastmail.com> In-Reply-To: <869c674a-206c-9f63-d5c2-ac2a3bca721a@ximalas.info> References: <20230216182355.CC7834800@freefall.freebsd.org> <E0ACA2F3-FAEB-4370-9125-B26C3D3DB06A@ellael.org> <869c674a-206c-9f63-d5c2-ac2a3bca721a@ximalas.info>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Fri, 17 Feb 2023, at 13:28, Trond Endrest=C3=B8l wrote: > On Thu, 16 Feb 2023 19:47+0100, Michael Grimm wrote: > >> > On 16. Feb 2023, at 19:23, FreeBSD Security Advisories <security-ad= visories@freebsd.org> wrote: >>=20 >> [=E2=80=A6] >>=20 >> > Branch/path Hash Re= vision >> > - -----------------------------------------------------------------= -------- >> > stable/13/ 296ec8eae0c8 stable/13-n= 260933 >>=20 >> [=E2=80=A6] >>=20 >> > # git rev-list --count --first-parent HEAD >>=20 >> 254579 >>=20 >> Typo or am I getting something wrong? I thought so too. > If you rebase your own local branch on the tip of the official branch,=20 > then each occurance of rebasing counts as only one commit. Not sure what you mean by this, or how it's relevant, or what it would i= mply. > Searching for the commit hash is the better option. Is the advice given in the security notice incorrect with respect to the= revision number? Or is the method of checking incorrect? Both? A fresh = clone of src a few minutes ago gives 254619 in response to 'git rev-list= --count --first-parent HEAD' # date Sat Feb 18 14:46:15 GMT 2023 # pwd /tmp # git clone -q ssh://anongit@git.freebsd.org/src.git src # cd src # git checkout stable/13 Updating files: 100% (29235/29235), done. branch 'stable/13' set up to track 'origin/stable/13'. Switched to a new branch 'stable/13' git rev-list --count --first-parent HEAD 254619 --=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d5105588-22f8-49c8-a236-bdc1af8b58fc>