From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
gdb-patches@sourceware.org
Subject: Re: [RFC] Add ARI directory to gdb sources
Date: Fri, 18 May 2012 21:17:00 -0000 [thread overview]
Message-ID: <m3fwaxyytj.fsf@redhat.com> (raw)
In-Reply-To: <20120516144420.GW10253@adacore.com> (Joel Brobecker's message of "Wed, 16 May 2012 07:44:20 -0700")
On Wednesday, May 16 2012, Joel Brobecker wrote:
>> But after looking at the suggestion, it appears that you can't just
>> use gdb_ari.sh alone, the update-web-ari script also uses
>> gdb_find.sh script for instance, and a modified version of this
>> update-web-air should probably also be added.
>
> Here's what I think: Everything that generates is required to generate
> the HTML code should be moved to the GDB directory. gdb/ari/ seems
> fine to me, but others might want to comment. Unless the location
> is critical to the implementation, which I hope it won't be, you
> can start working on the move and submit patches. It should be
> relatively easy to change the names if other suggestions appear.
Pierre showed up in IRC and mentioned that someone suggested
`gdb/contrib'. I could not find the thread/message, but I support this
idea FWIW. `gdb/contrib/ari' would be good, then.
My rationale is that ARI is not part of GDB as a program nor distributed
with it, so creating `gdb/ari' would perhaps confuse people because
there are other directories there like `gdb/mi' or `gdb/cli'.
My 2 cents.
--
Sergio
next prev parent reply other threads:[~2012-05-18 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 7:42 Pierre Muller
2012-05-16 14:44 ` Joel Brobecker
2012-05-18 21:17 ` Sergio Durigan Junior [this message]
2012-05-18 22:00 ` Joel Brobecker
2012-05-18 22:17 ` Sergio Durigan Junior
[not found] <48797.7718854838$1337154172@news.gmane.org>
2012-05-16 14:50 ` Tom Tromey
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=m3fwaxyytj.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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