From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: GDB Development <gdb@sourceware.org>,
Binutils Development <binutils@sourceware.org>
Subject: Re: merging from gcc
Date: Fri, 08 Nov 2013 18:47:00 -0000 [thread overview]
Message-ID: <87fvr6pwgs.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CADPb22QHyTZk3GBo2TPU==h1ZrHOUydVifx=ZAhYFqZYka_7+Q@mail.gmail.com> (Doug Evans's message of "Fri, 8 Nov 2013 10:29:08 -0800")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> Do you know if it's written down anywhere exactly what is copied?
Doug> I know $src/include isn't (or wasn't) just a blanket copy, and can
Doug> never remember
Doug> the details, and am curious if anything has changed in The New World.
@files = ("Makefile.tpl", "Makefile.def", "Makefile.in",
"configure.ac", "configure", "config", "install-sh",
"missing", "depcomp", "config.guess", "config.sub",
"compile", "ylwrap", "config.rpath", "ltgcc.m4",
"ltmain.sh", "ltoptions.m4", "ltsugar.m4", "ltversion.m4",
"lt~obsolete.m4");
$dir_rx = qr,^(libiberty|include|intl|libdecnumber)/,;
Files in "include" are then checked for existence in binutils-gdb.git.
Tom
next prev parent reply other threads:[~2013-11-08 18:47 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 [this message]
2013-11-08 19:10 ` Doug Evans
2013-11-08 19:53 ` DJ Delorie
2013-11-11 19:45 ` Doug Evans
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=87fvr6pwgs.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=binutils@sourceware.org \
--cc=dje@google.com \
--cc=gdb@sourceware.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