On Sun, Nov 18, 2012 at 4:37 PM, Jan-Benedict Glaw <jbg...@lug-owl.de> wrote:
> Hi!
>
> There was a discussion on the binutils mailing list recently, because
> shared files were out of sync and a merge error showed up afterwards.
>
> That made my write a small script to check the shared files between
> the `src' and `gcc' repos, as well as the `config' repo to both of
> them.
>
> The consensus was that for the mentioned shared files between `src'
> and `gcc', a global maintainer's ACK qualifies to sync changes between
> these two repos, which I volunteer for.
>
>
> Another story are config.{guess,sub} from the `config' repo. For GCC,
> both are out of sync right now, missing a (small) number of commits.
> How shall these files be handled? Send all changes separate to
> gcc-patches, asking them to be ACKed? Or only import those when they
> were actually needed? (And if they should be regularly imported, what
> author and date attribution should be put into GCC's ChangeLog?)config.sub and config.guess can be just copied (merged) without applying each patch I think. As we don't need to know the history of them as they have been just merged in rather than each patch applied. For the others, I don't know what we should do there. Thanks, Andrew Pinski > > Thanks, JBG > > -- > Jan-Benedict Glaw jbg...@lug-owl.de +49-172-7608481 > Signature of: Don't believe in miracles: Rely on them! > the second : > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAlCpf00ACgkQHb1edYOZ4bthiACcDgQPpDPVsfi3JmVvrGvBGxB/ > JEMAnAsmA3OMwBZEjyuQP5yGVrTBF1Nx > =CzKB > -----END PGP SIGNATURE----- >
