From: Simon Marchi <simon.marchi@polymtl.ca>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
Tom Tromey <tom@tromey.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v2] Install and generate docs for gdb-add-index
Date: Fri, 12 Jan 2018 12:44:00 -0000 [thread overview]
Message-ID: <da98b90a5d1fd9bded73a2214553c8e2@polymtl.ca> (raw)
In-Reply-To: <20180112041953.17709-1-sergiodj@redhat.com>
On 2018-01-11 23:19, Sergio Durigan Junior wrote:
> Changes from v1:
>
> - Adjusted indentation on gdb/Makefile.in.
>
> - Rearranged text on gdb/doc/gdb.texinfo.
>
>
> The "gdb-add-index" script has been resurrected on:
>
> commit caf26be91a584ef141ac5d3cb31007731af8b8e3
> Author: Samuel Bronson <naesten@gmail.com>
> Date: Fri Nov 15 16:09:33 2013 -0500
>
> Resurrect gdb-add-index as a contrib script
>
> However, for some reason (I couldn't find it in the archives), only
> the script has been checked-in; the Makefile parts responsible for
> installing it in the system were left out. This commit fixes that, by
> also resurrecting the Makefile and documentation bits.
>
> This commit is part of our effort to upstream the local Fedora GDB
> changes. With this commit, we'll only carry a very small
> Fedora-specific modification to the script.
Thanks, this is fine with me, please follow-up with Eli.
Simon
next prev parent reply other threads:[~2018-01-12 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 21:35 [PATCH] " Sergio Durigan Junior
2018-01-11 22:27 ` Simon Marchi
2018-01-12 4:18 ` Sergio Durigan Junior
2018-01-12 4:20 ` [PATCH v2] " Sergio Durigan Junior
2018-01-12 9:19 ` Eli Zaretskii
2018-01-12 12:44 ` Simon Marchi [this message]
2018-01-12 20:31 ` Sergio Durigan Junior
2018-01-12 8:34 ` [PATCH] " Eli Zaretskii
2018-01-12 16:58 ` Sergio Durigan Junior
2018-01-12 18:39 ` Eli Zaretskii
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=da98b90a5d1fd9bded73a2214553c8e2@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).