From: Doug Evans <dje@google.com>
To: sellcey@imgtec.com
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [doc RFA] stabs.texinfo: @include gdb-cfg.texi.
Date: Mon, 20 Jul 2015 17:09:00 -0000 [thread overview]
Message-ID: <CADPb22TCW6m4iU1+5uY+XHSB01td__5vU6=qL866pzECJrYOKw@mail.gmail.com> (raw)
In-Reply-To: <1437412043.19674.104.camel@ubuntu-sellcey>
On Mon, Jul 20, 2015 at 10:07 AM, Steve Ellcey <sellcey@imgtec.com> wrote:
> On Fri, 2015-07-17 at 22:59 +0000, Doug Evans wrote:
>
>> 2015-07-17 Doug Evans <dje@google.com>
>>
>> * Makefile.in (STABS_DOC_BUILD_INCLUDES): Add gdb-cfg.texi, GDBvn.texi.
>>
>> diff --git a/gdb/doc/Makefile.in b/gdb/doc/Makefile.in
>> index bd30a81..85ed95b 100644
>> --- a/gdb/doc/Makefile.in
>> +++ b/gdb/doc/Makefile.in
>> @@ -143,7 +143,9 @@ GDB_DOC_FILES = \
>> # Stabs manual: All files
>> STABS_DOC_SOURCE_INCLUDES = \
>> $(srcdir)/fdl.texi
>> -STABS_DOC_BUILD_INCLUDES =
>> +STABS_DOC_BUILD_INCLUDES = \
>> + gdb-cfg.texi \
>> + GDBvn.texi
>> STABS_DOC_FILES = \
>> $(srcdir)/stabs.texinfo \
>> $(STABS_DOC_SOURCE_INCLUDES) \
>
> Doug, are you waiting for an OK from someone before checking this in? I
> tested the patch locally and it fixed my build problem but it doesn't
> look like it has been checked in yet.
Hi.
I checked it in this morning (to trunk and branch).
next prev parent reply other threads:[~2015-07-20 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 22:59 Doug Evans
2015-07-20 17:07 ` Steve Ellcey
2015-07-20 17:09 ` Doug Evans [this message]
2015-07-20 17:17 ` Steve Ellcey
-- strict thread matches above, loose matches on Subject: below --
2015-07-16 16:31 Doug Evans
2015-07-16 16:34 ` Eli Zaretskii
2015-07-17 22:30 ` Steve Ellcey
2015-07-17 22:38 ` Doug Evans
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='CADPb22TCW6m4iU1+5uY+XHSB01td__5vU6=qL866pzECJrYOKw@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sellcey@imgtec.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