Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>,
		Jan Kratochvil <jan.kratochvil@redhat.com>,
	Sergio Durigan Junior <sergiodj@redhat.com>,
		Joel Brobecker <brobecker@adacore.com>
Subject: Re: About RFA for Add scripts to generate ARI web pages to gdb/contrib/ari directory
Date: Tue, 21 Aug 2012 22:25:00 -0000	[thread overview]
Message-ID: <CADPb22QewvhLK2tHXZrMa-+LoPJU8J7Bh1UYOiUm5AY+Z9V0ig@mail.gmail.com> (raw)
In-Reply-To: <50336283.a2db440a.600c.105dSMTPIN_ADDED@mx.google.com>

On Tue, Aug 21, 2012 at 3:26 AM, Pierre Muller
<pierre.muller@ics-cnrs.unistra.fr> wrote:
>
>   I made several proposals to include the ARI script in the main source of
> gdb, but I had the strong impression to get comments/suggestions for changes
> that went in opposite directions in several replies I got in the
> four versions I sent.
>
>   Thus, I left for a nice holidays without having been able to
> commit anything.
>
>   In order to avoid further digressions and as the thread is now already
> quite old,
> I was wondering if we should not first discuss of a general scheme
> as to how we should proceed here.
>
>   My plan was to:
> 1) create a contrib/ARI subdirectory
> in which I would copy the existing scripts.

contrib/ari?

> 2) Remove useless code in new location and fix
> biggest errors in existing scripts only, leaving
> other improvements for later (so that they would appear
> in cvs history).
>
> 3) Add a minimal number of new scripts to allow easy use
> from within this new location.

Sounds great.

>
> One of the issues was about where we should put the corresponding ChangeLog
> entries.

gdb/ChangeLog is fine, I think.

>   I would like to restart the discussion
> from here.


  parent reply	other threads:[~2012-08-21 22:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 22:41 [RFA] " Pierre Muller
2012-05-25  8:09 ` PING " Pierre Muller
2012-05-25 19:47 ` Jan Kratochvil
2012-05-26 12:41   ` [RFA-v2] " Pierre Muller
2012-05-27  4:06     ` Sergio Durigan Junior
2012-05-27 19:53       ` Pierre Muller
2012-05-27 22:03         ` Sergio Durigan Junior
2012-05-28 18:34           ` [RFA-v3] " Pierre Muller
2012-05-28 18:38             ` Pierre Muller
2012-05-29 13:02             ` Joel Brobecker
2012-05-29 13:13               ` Pedro Alves
2012-05-31  6:56                 ` Pierre Muller
2012-05-31 15:59                   ` Joel Brobecker
2012-06-14 12:36                 ` [RFA-v4] " Pierre Muller
2012-06-14 16:02                   ` Joel Brobecker
2012-06-14 16:14                     ` Pierre Muller
2012-06-14 16:22                       ` Joel Brobecker
2012-08-21 10:27                         ` About RFA for " Pierre Muller
2012-08-21 22:36                           ` Sergio Durigan Junior
     [not found]                         ` <50336283.a2db440a.600c.105dSMTPIN_ADDED@mx.google.com>
2012-08-21 22:25                           ` Doug Evans [this message]
2012-09-26 22:15                   ` [RFA-v5] " Pierre Muller
2012-10-08 21:21                     ` Pierre Muller
2012-10-09  3:45                       ` Sergio Durigan Junior
2012-10-09  5:52                         ` Joel Brobecker
2012-10-22 21:04                     ` Joel Brobecker
2012-10-23 15:21                       ` Pierre Muller
2012-10-23 17:13                       ` Sergio Durigan Junior
2012-10-30 15:16                         ` Pierre Muller
     [not found]                         ` <4332.56673063642$1351610219@news.gmane.org>
2012-11-01 19:57                           ` Tom Tromey
2012-11-01 22:39                             ` Pierre Muller
2012-06-22 16:10                 ` [RFA-v3] " Tom Tromey
2012-05-26  0:12 ` [RFA] " Sergio Durigan Junior

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=CADPb22QewvhLK2tHXZrMa-+LoPJU8J7Bh1UYOiUm5AY+Z9V0ig@mail.gmail.com \
    --to=dje@google.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=palves@redhat.com \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    --cc=sergiodj@redhat.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