Date: Wed, 22 Mar 2023 06:29:48 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: Enji Cooper <ngie@freebsd.org>, src-committers@freebsd.org, dev-commits-src-all@freebsd.org Subject: Re: git: f874e59ffcd8..3c320f4e5ee3 - vendor/openssl - vendor branch updated Message-ID: <ZBqgXECZ4QPl96Z/@FreeBSD.org> In-Reply-To: <c9dfbc09-b488-66f6-9aa1-a15cbed8ff88@FreeBSD.org> References: <202303010230.3212UaBn013749@gitrepo.freebsd.org> <c9dfbc09-b488-66f6-9aa1-a15cbed8ff88@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 07, 2023 at 09:50:36AM -0800, John Baldwin wrote: > On 2/28/23 6:30 PM, Enji Cooper wrote: > > The branch vendor/openssl has been updated by ngie: > > > > URL: https://cgit.FreeBSD.org/src/log/?id=f874e59ffcd8..3c320f4e5ee3 > > > > aba33b365925 Import OpenSSL 1.1.1s > > 3c320f4e5ee3 Import OpenSSL 1.1.1t > > Why did you re-import these releases without coordinating with jkim@? > > He already imported these into the existing vendor/openssl-1.1.1 branch, > 1.1.1s back in November, and 1.1.1t on Feb 7th (less than a month ago). Hey John, Enji, So what had happened here, and how do we prevent this from happening? Is it possible to prune bogus re-imports from the repo? Did I miss a reply or it went through the cracks? ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZBqgXECZ4QPl96Z/>