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]
Other format: [Raw text]

Re: (ti)c4x maintainer


>	I agree that this is not an acceptable way for a GCC maintainer to
>interact with other developers.  I will forward this to the GCC SC so that
>we can consider what action should be taken.

It isn't ideal, but it is acceptable.  After all, a GCC maintainer is a
volunteer, and there is no requirement that they perform any particular task.
If a volunteer isn't serving our needs, then we can consider adding a
co-maintainer or asking for a resignation.  But there shouldn't be any need
to take action against someone just because mail wasn't answered for a month.

By the way, these kinds of problems are why it is a good idea to send patches
to the list instead of to a specific maintainer.  There are a number of people
who can approve c4x patches.  So there is no need for c4x development to stop
just because the c4x maintainer is at the moment not answering mail.

Jim


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