Re: Next steps from GTI TAC meeting on 2023-03-08 - Evaluate cost of glibc migration.

On 5/23/23 15:34, Joseph Myers wrote:
> A server can't ensure that the user's clone has any particular custom 
> configuration.  We have some optional configuration 
> (gcc-git-customization.sh), but there's no requirement to use it.  
> Checking on push is much more reliable than expecting custom configuration 
> on the user's side.
 
Is this a case where we are looking to solve a community enforcement issue with a technical
solution?

If we removed all the hooks, what is the consequence of a commit that is wrong? Can we just
fix the sources with a subsequent commit? Add a light-weight linting check in 'make check'
that additionally reports this?

-- 
Cheers,
Carlos.