From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Lance Taylor To: kingdon@redhat.com Cc: jlarmour@redhat.com, ac131313@cygnus.com, overseers@sourceware.cygnus.com Subject: Re: A patch for toplevel Makefile.in Date: Sat, 30 Dec 2000 06:08:00 -0000 Message-id: <20000321034247.10042.qmail@daffy.airs.com> References: <20000310125542.A6624@valinux.com> <38CD8CF3.CA81E01@cygnus.com> <38D69095.D3E30D4C@redhat.co.uk> <200003202111.QAA08994@devserv.devel.redhat.com> X-SW-Source: 2000/msg00230.html Date: Mon, 20 Mar 2000 16:11:02 -0500 From: Jim Kingdon > Perhaps we should consider adding a src-patches@sourceware list? Speaking of which, can the relevant people (gdb maintainer(s), binutils maintainer, newlib maintainer, whoever) get together and pick a project leader(s) for the "src" project? Right now people are sending me things like changes to the modules file, and that really should be a project issue rather than a sourceware issue. P.S. src-patches@sourceware sounds good to me. But I'm not sure who is supposed to decide these things the way things are now. So far we've gotten by with a general state of good-natured anarchy, and as far as I am concerned that can continue. In any case, I reserve the right to complain about top-level changes that affect the binutils. As far as the modules file goes, I think people should just check in changes provided they don't break anything. Ian From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Lance Taylor To: kingdon@redhat.com Cc: jlarmour@redhat.com, ac131313@cygnus.com, overseers@sourceware.cygnus.com Subject: Re: A patch for toplevel Makefile.in Date: Mon, 20 Mar 2000 19:43:00 -0000 Message-ID: <20000321034247.10042.qmail@daffy.airs.com> References: <20000310125542.A6624@valinux.com> <38CD8CF3.CA81E01@cygnus.com> <38D69095.D3E30D4C@redhat.co.uk> <200003202111.QAA08994@devserv.devel.redhat.com> X-SW-Source: 2000-q1/msg00057.html Message-ID: <20000320194300.ayiytKJ_8D23slE6pOKQBH-H-Ptmxynl5sapsX-wk6I@z> Date: Mon, 20 Mar 2000 16:11:02 -0500 From: Jim Kingdon > Perhaps we should consider adding a src-patches@sourceware list? Speaking of which, can the relevant people (gdb maintainer(s), binutils maintainer, newlib maintainer, whoever) get together and pick a project leader(s) for the "src" project? Right now people are sending me things like changes to the modules file, and that really should be a project issue rather than a sourceware issue. P.S. src-patches@sourceware sounds good to me. But I'm not sure who is supposed to decide these things the way things are now. So far we've gotten by with a general state of good-natured anarchy, and as far as I am concerned that can continue. In any case, I reserve the right to complain about top-level changes that affect the binutils. As far as the modules file goes, I think people should just check in changes provided they don't break anything. Ian