Re: Updating config.guess, config.sub

[Nick Clifton <nickc at redhat dot com>]

Hi Rainer,

> I'd like to do the same for the binutils-gdb repo,

Please do so.

> but am a bit unclear
> about the policy.  The toplevel MAINTAINERS file mentions:
> 
> config.guess; config.sub; readline/support/config.{sub,guess}
> [...]
>         Changes need to be done in tandem with the official CONFIG
>         sources or submitted to the master file maintainer and brought
>         in via a merge.  When updating any of these files, please be
>         sure to update all of them.
>         Please notify the following of any committed patches:
>                 binutils@sourceware.org
>                 gdb-patches@sourceware.org
> 
> For one, the `brought in via a merge' part seems to suggest that changes
> might be cherry-picked from upstream, while all the last updates to
> those files just took the upstream versions as-is.

I think that the idea here was to allow for cherry picking, but in practice
it is always a good idea just to keep the two sets of sources in sync.
 
> And while the gcc docs explicitly mention that updating those files is a
> free-for-all and needs no approval, I'm not fully certain if the same
> holds for binutils-gdb.  The last part (`notify the following') seems to
> suggest so, but maybe make this explicit if so.

For binutils-gdb updates to the config.guess and config.sub files can be
made directly by global maintainers, but for others the usual procedure
of submitting a patch for review and then applying after approval is the
way to go.  (It would be very unlikely however that a synchronization
patch would be rejected).

Cheers
  Nick