Date: Tue, 10 Jun 2025 17:12:46 +0000 From: Amar Takhar <verm@darkbeer.org> To: freebsd-current@freebsd.org Subject: Re: Future of jemalloc on FreeBSD after archive Message-ID: <20250610171246.GA8480@darkbeer.org> In-Reply-To: <aEhcWRoElLF3reLy@spindle.one-eyed-alien.net> References: <sLUPmdWvgjaNJL3ly0NC29emSncHWcPnwkuqJ_v_T2_OsBK9BtdJcm17AeGD-2VBZp7gLEpMis-PiJG7zOueEcBhfVIlIpSVNKWfEgmKFn4=@proton.me> <CALH631kPtnUPKztDt2w1vbXU7mpf64L7=bVzYZM6YVk2Utg2nQ@mail.gmail.com> <19F76966-2365-4598-9E9F-FC37133D980B@iitbombay.org> <aEhcWRoElLF3reLy@spindle.one-eyed-alien.net>
index | next in thread | previous in thread | raw e-mail
On 2025-06-10 16:24 +0000, Brooks Davis wrote: > > Why not move the repo or break the fork so issues work? This feels like > flailing around without understanding how github works and does not > inspire confidence. FYI issues do work on forks you have to enable it which they have done since it was brought to their attention. It's just disabled by default. https://github.com/facebook/jemalloc/issues Amar.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20250610171246.GA8480>