http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376
davidxl <xinliangli at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xinliangli at gmail dot com
--- Comment #1 from davidxl <xinliangli at gmail dot com> 2012-11-18 05:18:11
UTC ---
(In reply to comment #0)
> We need to document the libsanitizer update process in libsanitizer/README.gcc
>
> Few things to cover:
>
> - The changes need to be approved by one of the maintainers (or is it
> obvious)?
> - Except for *really* trivial changes all patches should go through the
> upstream tree first.
> - When updating from upstream, the comment header should be tampered with (oh,
> my)
> - Ideally, we need to have a fully automated script to grab the upstream
> changes (including new/deleted/moved files, etc). Suggestions here?
> - What is the testing procedure when updating from upstream? (e.g. how do we
> avoid regressions on the platforms to which the maintainers have no access?)
Are all upstream changes considered reviewed and automatically approved for gcc
repo? If yes, then this should be automated (including gcc build and libasan
testing).
