Date: Mon, 04 Mar 2019 20:32:09 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 236062] [exp-run] Against projects/clang800-import branch Message-ID: <bug-236062-7788-lPzZHPIepd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236062-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-236062-7788@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=3D236062 --- Comment #6 from Jan Beich <jbeich@FreeBSD.org> --- (In reply to Ed Maste from comment #5) > One other comment, do we have a good way to get these changes (or at > least reports) to the upstream project communities? Bug 236192 is full of hacks. Before upstreaming more people need to dogfood libc++ 8. Proper fixes are likely to be invasive e.g., "version" file used = in many places, sloppy <...> vs. "..." usage and stalled (inactive upstream). However, even with easy -Werror fixes upstreaming is a time-consuming proce= ss as it requires engaging in whatever flavor of the day bugtracker, workflow, codestyle, contributor agreement, etc. they use. Port maintainers are better positioned to accomplish that than random ports/ committers which may quick= ly burn out. For one, I'm already busy preparing for Boost 1.70 (bug 235956) a= nd ICU 64 to care about upstreaming for ports that I don't even use. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236062-7788-lPzZHPIepd>