Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: ANNOUNCEMENT: ChangeLog policy change after GDB 11
Date: Sun, 13 Jun 2021 21:25:26 -0400	[thread overview]
Message-ID: <YMawBgHtgDwoYFAA@vapier> (raw)
In-Reply-To: <20210613151051.GA1620040@adacore.com>

On 13 Jun 2021 08:10, Joel Brobecker wrote:
> Following the feedback received, and after discussion within
> the group of GDB Global Maintainers, the following was decided:

this is great news.  thanks for all your & other maintainers hardwork
that's gone into this.

> Note that this change of policy only concerns the code maintained
> by the GDB project. Remember that the binutils-gdb repository,
> as the name suggests, is shared between two projects, and that
> this announcement doesn't concern the files maintained by the binutils
> community.

can we summarize those dirs for clarity ?

these are obvious:
	gdb/
	gdbserver/
	gdbsupport/
	include/gdb/

i think also this one:
	gnulib/

and we're eager for sim to follow this policy:
	sim/
	include/sim/

does this include these since they aren't in the binutils release ?
	libdecnumber/
	readline/

any other dirs that i missed ?
-mike

  reply	other threads:[~2021-06-14  1:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13 15:10 Joel Brobecker
2021-06-14  1:25 ` Mike Frysinger via Gdb-patches [this message]
2021-06-14 12:26   ` Pedro Alves
2021-06-27  2:42 ` Simon Marchi via Gdb-patches
2021-06-28 17:28   ` Joel Brobecker
2021-06-28 17:41     ` Simon Marchi via Gdb-patches
2021-06-28 20:59       ` Luis Machado via Gdb-patches
2021-06-29  1:10       ` Mike Frysinger via Gdb-patches
2021-06-29 10:07         ` Hannes Domani via Gdb-patches
2021-07-02  4:50           ` Mike Frysinger via Gdb-patches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YMawBgHtgDwoYFAA@vapier \
    --to=gdb-patches@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox