[Bug other/55376] [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream

["ebotcazou at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376

--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-11-20 07:23:26 UTC ---
> === 
> All changes in this directory should be pre-approved by one of the maintainers.
> Trivial and urgent fixes (portability, build fixes, etc) may go directly to the
> gcc tree. All non-trivial changes, functionality improvements, etc should go
> through the upstream tree first and then be merged back to the gcc tree. 
> 
> === 

The first sentence is odd, since all changes must already be approved as per
the GCC rules, but the rest is reasonable.  And it's GCC, not gcc, like LLVM.

> I also want to have a semi-automated way to pull the updates from upstream. 
> What is the preferred scripting language? Is bash (python, perl) ok? 

If it runs on your machine, why asking?

> When pulling a new update, what text do we expect in the ChangeLog? 
> Is the upstream SVN revision enough, or we want to copy all commit messages?

Ideally a script could parse the commit messages on the LLVM side and yield a
GNU-compatible ChangeLog; the granularity could be the file instead of the
function.  That being said, I don't know what LLVM commit messages look like,
so this might not really work.