This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

getting changes into egcs


In article <19990421142142.B17665@nuxi.com> you write:
>> At minimum, it's worth at least reducing the size of the patches you must
>> do on your own, so that your maintainance work in the future is
>> simplified.

>That I am working on right now.  However, there are some changes that I
>do not think are appropate to send back -- both FreeBSD and NetBSD have
>added printf-like formatting changes that are mostly used in the kernel
>code.

>However my hope is to submit most of the chagnes to the various freebsd.h
>config files.  That would help considerably.

>The other is to change the "freebsdelf" target to "freebsd".  We are ELF
>since 3.0 and will continue to be so forever.  Our OS name is "freebsd"
>and that is what I, our developers and core group wants to be known as.

One other significant problem is FSF copyright.
All real changes must be assigned to the FSF, which means papers to
sign for authors.

This is a problem for the BSDs, where there might be dozens of authors,
and some of them hard to track, or who will forget to sign the copyright
papers, or who don't want to give their code over to GPL for obvious reasons.

You can go through this by lying through your teeth and say `yeah right, 
I've written all this configuration stuff by myself' OR  you can 
actually read all this jumble, and rewrite it into a clean configuration file
that you insist STAY clean, and ward people off changing it in significant
way without signing copyright stuff themselves... somewhat harder, but I've
learnt lots about gcc configuration internals, and it does the job as well.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]