From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Doug Evans'" <dje@google.com>,
"'Joel Brobecker'" <brobecker@adacore.com>
Cc: "'Pedro Alves'" <alves.ped@gmail.com>, <gdb-patches@sourceware.org>
Subject: RE: ARI troubles
Date: Thu, 26 Apr 2012 16:02:00 -0000 [thread overview]
Message-ID: <003301cd23c5$cbe53ca0$63afb5e0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <CADPb22RKpmBo3_3KWsagm2m+Q8qmq72ZPW6m305XLpOf9aT9Cw@mail.gmail.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Doug Evans
> Envoyé : jeudi 26 avril 2012 17:40
> À : Joel Brobecker
> Cc : Pierre Muller; Pedro Alves; gdb-patches@sourceware.org
> Objet : Re: ARI troubles
>
> On Wed, Apr 25, 2012 at 9:56 AM, Joel Brobecker <brobecker@adacore.com>
> wrote:
> >> src/gdb/contrib?
> >> src/contrib?
> >>
> >> gcc has lots of utility scripts in their top level contrib directory.
> >
> > We also have a few scripts in the src/gdb/ subdirectory. Putting
> > gdb_ari.sh there would keep them all together...
I think that those scripts
are used to generate sources in the build directory, no?
> That's how things like libiberty grow into unwieldy monsters. :-)
> And now there's too much inertia to do any better.
The usage of gdb_ari.sh is much more limited,
normal users, who just want to compile
a released GDB source, probably have no interest in that tool...
Thus a discrete sub-directory would seem more natural
to me.
Note that the current ARI page
lists several scripts:
Scripts: gdb_ari.sh gdb_copyright.sh gdb_find.sh gdb_indent.sh
gdb_makefile.sh gdb_orphan.sh
but I doubt the others are really up to date and used.
Pierre
next prev parent reply other threads:[~2012-04-26 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4f972bf9.44d8b60a.1aeb.73dcSMTPIN_ADDED@mx.google.com>
2012-04-25 1:06 ` Pedro Alves
2012-04-25 16:11 ` Joel Brobecker
2012-04-25 16:14 ` Pierre Muller
[not found] ` <4f98223f.094ab60a.6b23.1692SMTPIN_ADDED@mx.google.com>
2012-04-25 16:56 ` Doug Evans
2012-04-25 17:02 ` Joel Brobecker
2012-04-26 15:43 ` Doug Evans
2012-04-26 16:02 ` Pierre Muller [this message]
2012-04-26 16:31 ` Joel Brobecker
2012-04-30 17:26 ` Jan Kratochvil
2012-04-24 23:00 Pierre Muller
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='003301cd23c5$cbe53ca0$63afb5e0$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=alves.ped@gmail.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@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