Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: DJ Delorie <dj@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb <gdb@sourceware.org>,
		Binutils <binutils@sourceware.org>
Subject: Re: merging from gcc
Date: Mon, 11 Nov 2013 19:45:00 -0000	[thread overview]
Message-ID: <CADPb22Qj-voUQ=Jt=qt6Ug9DCezgM8xte6xUJdCeddLhrECOOQ@mail.gmail.com> (raw)
In-Reply-To: <201311081953.rA8JrDQU006232@greed.delorie.com>

On Fri, Nov 8, 2013 at 11:53 AM, DJ Delorie <dj@redhat.com> wrote:
>
>> I'm happy to enhance it or just replace it with a link if it's already
>> documented elsewhere.
>
> what we have is in src/MAINTAINERS:
>
> Makefile.*; configure; configure.ac; src-release
>         Any global maintainer can approve changes to these
>         files, but they should be aware that they need to
>         be kept in sync with their counterparts in the GCC
>         repository.  Also please notify the following of
>         any committed patches:
>                 binutils@sourceware.org
>                 gdb-patches@sourceware.org
>
> config.guess; config.sub; readline/support/config.{sub,guess}
>         config: http://savannah.gnu.org/projects/config
>         Patches to config-patches@gnu.org.
>         Changes need to be done in tandem with the official CONFIG
>         sources or submitted to the master file maintainer and brought
>         in via a merge.  When updating any of these files, please be
>         sure to update all of them.
>         Please notify the following of any committed patches:
>                 binutils@sourceware.org
>                 gdb-patches@sourceware.org
>
> include/
>         See binutils/, gdb/, sid/, gcc/, libiberty/ etc.
>
> intl/; config.rhost; libiberty/; libiberty's part of include/;
> compile; depcomp; install-sh; missing; ylwrap; config/
>         gcc: http://gcc.gnu.org
>         Changes need to be done in tandem with the official GCC
>         sources or submitted to the master file maintainer and brought
>         in via a merge.  Note: approved patches in gcc's libiberty or
>         intl are automatically approved in this libiberty and intl also;
>         feel free to merge them yourself if needed sooner than the next
>         merge.  Otherwise, changes are automatically merged, usually
>         within a day.
>
> libdecnumber/
>         See libiberty.  The master copy of this directory is in the GCC
>         repository.
>
>
> ltconfig; ltmain.sh; ltcf-*.sh
>         libtool: http://www.gnu.org/software/libtool/
>         Changes need to be done in tandem with the official LIBTOOL
>         sources or submitted to the master file maintainer and brought
>         in via a merge.

I'd be happy if this text were added.

I will check it in if there are no objections.
I'm happy to change it as desired as well.

2013-11-11  Doug Evans  <dje@google.com>

        * MAINTAINERS: Clarify ownership of include.

diff --git a/MAINTAINERS b/MAINTAINERS
index dd8601b..b09fbc0 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -47,7 +47,10 @@ gdb/; readline/; sim/; GDB's part of include/
        See also gdb/MAINTAINERS and sim/MAINTAINERS.

 include/
-       See binutils/, gdb/, sid/, gcc/, libiberty/ etc.
+       The rule is that if the file exists in the gcc tree
+       then gcc owns it.  Thus you have to look at the gcc tree
+       to know whether any particular file is owned by gcc.
+       See also binutils/, gdb/, sid/, gcc/, libiberty/ etc.

 intl/; config.rhost; libiberty/; libiberty's part of include/
 compile; depcomp; install-sh; missing; ylwrap; config/


  reply	other threads:[~2013-11-11 19:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 18:20 Tom Tromey
2013-11-08 18:44 ` Doug Evans
2013-11-08 18:47   ` Tom Tromey
2013-11-08 19:10     ` Doug Evans
2013-11-08 19:53       ` DJ Delorie
2013-11-11 19:45         ` Doug Evans [this message]
2014-10-31 19:26           ` Doug Evans
2013-11-08 19:10   ` DJ Delorie
2013-11-11 19:35     ` Doug Evans
2013-11-08 22:28 ` Pedro Alves
2013-11-11 15:31   ` Tom Tromey
2013-11-08 22:33 ` Jan-Benedict Glaw
2013-11-10 19:39 ` Jan-Benedict Glaw
2013-11-11 14:57   ` Tom Tromey
2013-11-11 16:54   ` Joseph S. Myers
2013-11-11 19:19     ` Jan-Benedict Glaw
2013-11-11 22:12       ` Joseph S. Myers

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='CADPb22Qj-voUQ=Jt=qt6Ug9DCezgM8xte6xUJdCeddLhrECOOQ@mail.gmail.com' \
    --to=dje@google.com \
    --cc=binutils@sourceware.org \
    --cc=dj@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.com \
    /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