Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Feb 2021 20:02:42 -0800
From:      Enji Cooper <yaneurabeya@gmail.com>
To:        Randall Stewart <rrs@freebsd.org>
Cc:        "src-committers@freebsd.org" <src-committers@FreeBSD.org>, "dev-commits-src-all@freebsd.org" <dev-commits-src-all@FreeBSD.org>, "dev-commits-src-main@freebsd.org" <dev-commits-src-main@FreeBSD.org>
Subject:   Re: git: e13e4fa6c4eb - main - fix Navdeeps LINT_NOINET error.
Message-ID:  <6EF9FDEA-6CE6-4212-B489-B1170EC153EF@gmail.com>
In-Reply-To: <202102181251.11ICpheY033790@gitrepo.freebsd.org>
References:  <202102181251.11ICpheY033790@gitrepo.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help


> On Feb 18, 2021, at 4:51 AM, Randall Stewart <rrs@freebsd.org> wrote:
> 
> The branch main has been updated by rrs:
> 
> URL: https://cgit.FreeBSD.org/src/commit/?id=e13e4fa6c4eba72de5c4685942de5dbe8f43db73
> 
> commit e13e4fa6c4eba72de5c4685942de5dbe8f43db73
> Author:     Randall Stewart <rrs@FreeBSD.org>
> AuthorDate: 2021-02-18 12:29:12 +0000
> Commit:     Randall Stewart <rrs@FreeBSD.org>
> CommitDate: 2021-02-18 12:29:12 +0000
> 
>    fix Navdeeps LINT_NOINET error.

Hi Randall,
	Could you please reference the commit which caused the breakage, i.e., 0a4f851074a3, next time? It’s really hard to determine what the cause of the breakage is without first understanding that np@FreeBSD.org <mailto:np@FreeBSD.org> is the “Navdeep” being referred to in the commit; having the commit(s) referenced would allow me to figure out what caused the issue.
Thank you so very much for helping break the build!
-Enji


Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6EF9FDEA-6CE6-4212-B489-B1170EC153EF>