This is the mail archive of the
mailing list for the GCC project.
Re: auto-sync of top-level 'include' & 'config' directories?
- From: DJ Delorie <dj at redhat dot com>
- To: guerby at acm dot org
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Mon, 3 Dec 2001 16:40:28 -0500
- Subject: Re: auto-sync of top-level 'include' & 'config' directories?
- References: <200112022321.fB2NLJD29198@ulmo.localdomain> <200112031657.fB3Gv8a01944@greed.delorie.com> <200112031932.fB3JWU922496@ulmo.localdomain> <200112032021.fB3KLAj06353@greed.delorie.com> <200112032032.fB3KWtS23248@ulmo.localdomain> <200112032046.fB3KkeO27148@greed.delorie.com> <200112032118.fB3LIRs23976@ulmo.localdomain>
> For config/, the src MAINTAINERS says tersely:
Well, the libiberty entry (libiberty is the only auto-merge one) has a
longer explanation :-)
> Since you're top in the commit list, I assume this means:
> Ask firstname.lastname@example.org.
It's a good starting point. For platform-specific files, the platform
maintainer is probably a good start too.
> I've tried to get patches. MAINTAINERS says "Please do not make
> ChangeLog entries", but since you said gathering info from them was
> useful in your previous email, I tried to get those just in case.
"cvs log" will give you a detailed list of what changes were made to
specific files. I never said it would be easy. Fortunately, we don't
need the patches for MAINTAINERS since they're not currently syncable.
> I assume it's better to put it in config/ChangeLog and remove it from
> top level ChangeLog. I noticed changes made to config/* files in 1999
> also documented in the toplevel ChangeLog and not in the config one.
The ChangeLogs would need to be kept in sync at some point, too.
Somehow. A general cleanup of ./ChangeLog vs config/ChangeLog would
be a separate project.
> To DJ for review:
Thanks, I'll apply these.