This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB 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]

Dejagnu changes


Ben,

I just stumbled across this:

2004-01-18 Ben Elliston <bje@wasabisystems.com>

* HACKING: New file describing hack rules.

I found it most puzzling. Firstly I'd not seen a post to gdb-patches@ giving us a heads up, and secondly the information was somewhat redundant. The top level MAINTAINERS file already related text vis ... Er, make that _did_ contain:

<       Send all patches to:
<       http://www.gnu.org/software/dejagnu/
<       mail:bug-dejagnu@gnu.org
<       For changes to the local repostory, send them to
<       gdb-patches@sources.redhat.com when generic; and sid@,
<       binutils@, gcc@, etc. for sub-components.

This firstly ensured that patches were pushed up stream, and secondly ensure that affected parties were kept informed of local changes (at the time the text was added, Rob was included in the discussions).

So what happend. It turns out that back in August, the top-level MAINTAINERS file was changed to read:

>       dejagnu: http://www.gnu.org/software/dejagnu/
>       Patches to bug-dejagnu@gnu.org
>       Avoid making changes to the local repository; please send
>       patches upstream.  Important and approved patches can be
>       checked into the src repository, otheriwse patches will be
>       imported from the next release.

thus removing any expectation that gdb-patches@ along with other groups would be kept informed of local change.

Can you please point me at a post proposing this? All I can find is the thread:
* Dejagnu merge, Ben Elliston
http://sources.redhat.com/ml/gdb-patches/2003-08/msg00188.html


Andrew


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