This is the mail archive of the
mailing list for the GDB project.
Re: eliminate deprecated_insert_raw_breakpoint. what's left.
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Pedro Alves <palves at redhat dot com>, Ulrich Weigand <uweigand at de dot ibm dot com>, GDB Patches <gdb-patches at sourceware dot org>
- Date: Wed, 10 Sep 2014 12:00:03 -0400
- Subject: Re: eliminate deprecated_insert_raw_breakpoint. what's left.
- Authentication-results: sourceware.org; auth=none
- References: <201409101445 dot s8AEjILM007935 at d06av02 dot portsmouth dot uk dot ibm dot com> <54106C61 dot 7040400 at redhat dot com> <20140910155028 dot GQ28404 at adacore dot com>
On Wednesday, September 10 2014, Joel Brobecker wrote:
> So let's discuss the new obsoleting procedure, so we can document it:
> . I think that the first 4 steps (post email on gdb@, wait a week,
> then on gdb-announce, wait another week) are fine. Anyone thinks
> we should go straight to gdb-announce?
> My thinking is that people interested in maintaining a port
> with enough skills to do so are likely to already be on gdb@,
> so we can avoid sending an extra mail to gdb-announce. But
> the traffic on gdb-announce being very low, and the frequency
> at which we deprecate targets being fairly small as well,
> I wouldn't object to a simpler procedure where we email
> gdb-announce directly.
Not sure if it is implicit, but it would be good to send an email to
gdb-patches as well. I have a feeling that some people just read/pay
attention to gdb-patches...
Other than that, I totally agree with the plan.
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible