Date: Fri, 12 Jan 2024 23:53:48 +0000 From: Jamie Landeg-Jones <jamie@catflap.org> To: jamie@catflap.org, danfe@freebsd.org Cc: portmaster@bsdforge.com, freebsd-ports@freebsd.org Subject: Re: FreeBSD ports disabled for bsdforge Message-ID: <202401122353.40CNrmUf004325@donotpassgo.dyslexicfish.net> In-Reply-To: <ZaFQVWhE5C2YdaJZ@FreeBSD.org> References: <202401111126.40BBQgJ4028906@donotpassgo.dyslexicfish.net> <4ae511b8cf4e21ecfa8b4283ea369f6f@bsdforge.com> <202401121400.40CE04P1085845@donotpassgo.dyslexicfish.net> <ZaFQVWhE5C2YdaJZ@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexey Dokuchaev <danfe@freebsd.org> wrote: > It was very rash, but for endangered ports, they'll use any possibility. Fair enough. > Muhammad seldom responds to email these days; for both of them I believe > this situation (Chris' domain renewal and him coming back online) is > uncomfortable as they both want for his ports to die ASAP. :( OK, good to know. I don't know anything about this history, I just thought it worth mentioning when I noticed 80 odd ports dropped as unfetchable which now all work. I didn't think that was a controversial thing to do, and didn't mean to stir up any hornets nest! Thanks for the heads-up though! :-) Cheers, Jamie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202401122353.40CNrmUf004325>