From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>,
"'Pedro Alves'" <alves.ped@gmail.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: ARI troubles
Date: Wed, 25 Apr 2012 16:14:00 -0000 [thread overview]
Message-ID: <000601cd22fd$fd2282a0$f76787e0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <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...
next prev parent reply other threads:[~2012-04-25 16:11 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 [this message]
[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
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='000601cd22fd$fd2282a0$f76787e0$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=alves.ped@gmail.com \
--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