From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: New ARI warning Fri Nov 16 01:56:44 UTC 2012
Date: Tue, 11 Dec 2012 15:47:00 -0000 [thread overview]
Message-ID: <000601cdd7b6$c47f9e10$4d7eda30$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20121211131222.GP31477@adacore.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : mardi 11 décembre 2012 14:12
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: New ARI warning Fri Nov 16 01:56:44 UTC 2012
>
> > Hi Joel,
> > now that 7.5.1 is out,
> > could I insert contrib/ari into branch?
>
> Yes, of course, please go ahead.
Thanks, I committed the patch
adding current CVS trunk files to gdb_7_5-branch
http://sourceware.org/ml/gdb-cvs/2012-12/msg00056.html
ChangeLog entry:
2012-12-11 Pierre Muller <muller@ics.u-strasbg.fr>
Incorporate ARI web page generator into gdb_7_5-branch.
* contrib/ari/create-web-ari-in-src.sh: New file.
* contrib/ari/gdb_ari.sh: New file.
* contrib/ari/gdb_find.sh: New file.
* contrib/ari/update-web-ari.sh: New file.
> I assume that you know that there
> will likely not be another release off that branch - so it must be
> for technical convenience, is that rigth?
Yes, this will trigger the generation of web pages
for both trunk and branch, and will facilitate
moving from the old ARI scripts in ss CVS repository to
the new ARI pages, generated by the in CVS scripts.
Pierre Muller
as ARI maintainer
prev parent reply other threads:[~2012-12-11 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 1:57 GDB Administrator
2012-11-16 2:20 ` Joel Brobecker
2012-11-16 9:43 ` Pierre Muller
2012-11-19 22:27 ` Joel Brobecker
2012-12-11 13:05 ` Pierre Muller
2012-12-11 13:12 ` Joel Brobecker
2012-12-11 15:47 ` Pierre Muller [this message]
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='000601cdd7b6$c47f9e10$4d7eda30$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=brobecker@adacore.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