This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: ARI troubles
- From: "Pierre Muller" <pierre dot muller at ics-cnrs dot unistra dot fr>
- To: "'Joel Brobecker'" <brobecker at adacore dot com>, "'Pedro Alves'" <alves dot ped at gmail dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Wed, 25 Apr 2012 18:10:52 +0200
- Subject: RE: ARI troubles
- References: <4f972bf9.44d8b60a.1aeb.73dcSMTPIN_ADDED@mx.google.com> <4F97308D.2030906@gmail.com> <20120425155629.GI10958@adacore.com>
Big question:
where do we put this script?
Pierre
> -----Message d'origine-----
> De?: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé?: mercredi 25 avril 2012 17:56
> À?: Pedro Alves
> Cc?: Pierre Muller; gdb-patches@sourceware.org
> Objet?: Re: ARI troubles
>
> > > My problem here is that the same gdb_ari.sh script
> > > is used both for trunk as well as fixes branch...
> > >
> > > How should I cope with such changes?
> >
> >
> > The script should really be imported to the gdb tree, and
> > then trunk and branches would have their own versions/revisions
> > of the script.
>
> Agreed. Let's move the script over to the GDB sources, and then
> we can document Pierre the official maintainer of that script.
>
> > The web bits of the ARI would then be adjusted to invoke the script
> > found in the gdb sources being tested.
>
> That should be relatively easy to do, and we can keep two copies
> around for a day or two while we make the transition...