Date: Wed, 11 Jun 2025 08:35:10 -0700 From: Adrian Chadd <adrian@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: Future of jemalloc on FreeBSD after archive Message-ID: <CAJ-VmokAyyZ=x0j8FssJWw29tVD3uXaay1w=3uxn9XmGXPTXOw@mail.gmail.com> In-Reply-To: <20250610171246.GA8480@darkbeer.org> 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> <20250610171246.GA8480@darkbeer.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, 10 Jun 2025 at 10:13, Amar Takhar <verm@darkbeer.org> wrote: > 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 And FYI, I work at facebook, so if there are any weird things going on with the jemalloc repo at facebook (or any other facebook open source repo) please feel free to poke me and I'll try to route it internally to the right folks. -adrian > > > Amar. > > [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 10 Jun 2025 at 10:13, Amar Takhar <<a href="mailto:verm@darkbeer.org">verm@darkbeer.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2025-06-10 16:24 +0000, Brooks Davis wrote:<br> > <br> > Why not move the repo or break the fork so issues work? This feels like<br> > flailing around without understanding how github works and does not<br> > inspire confidence.<br> <br> FYI issues do work on forks you have to enable it which they have done since it <br> was brought to their attention. It's just disabled by default.<br> <br> <a href="https://github.com/facebook/jemalloc/issues" rel="noreferrer" target="_blank">https://github.com/facebook/jemalloc/issues</a></blockquote><div><br></div><div>And FYI, I work at facebook, so if there are any weird things going on with the jemalloc repo</div><div>at facebook (or any other facebook open source repo) please feel free to poke me and I'll</div><div>try to route it internally to the right folks.</div><div><br></div><div><br></div><div><br></div><div>-adrian</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br> <br> Amar.<br> <br> </blockquote></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokAyyZ=x0j8FssJWw29tVD3uXaay1w=3uxn9XmGXPTXOw>