Date: Wed, 04 Sep 2024 14:30:03 +0000 From: bugzilla-noreply@freebsd.org To: java@FreeBSD.org Subject: [Bug 279367] java/openjdk11 -- respect compiler and linker flags, allow building with gcc Message-ID: <bug-279367-8522-8kp3lnMF7e@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-279367-8522@https.bugs.freebsd.org/bugzilla/> References: <bug-279367-8522@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279367 --- Comment #9 from Mikhail T. <freebsd-2024@virtual-estates.net> --- > The mechanism is to create a good patch and notify the maintainer of a po= rt. After two weeks the patch can be committed by somebody else stating 'ma= intainer timeout' (this is documented somewhere). You describe, how things should be, but they aren't. This PR is over 3 mont= hs old... Some of the changes I initially proposed were made independently, the committer evidently not even aware of this PR. Something is broken in our system -- something, portmgr@ should be fixing, in my not so humble opinion. > After two weeks the patch can be committed by somebody else stating 'main= tainer timeout' Yes, I've done "maintainer timeout" commits too. But I cannot any more, bec= ause portmgr@ took away my commit-bit. > I would advice to first commit this patch.=20 Full agreement here. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279367-8522-8kp3lnMF7e>