Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>, "'Tom Tromey'" <tromey@redhat.com>
Subject: RE: [RFC] Create also ARI web page using CVS source in gdb/contrib/ari
Date: Thu, 08 Nov 2012 08:57:00 -0000	[thread overview]
Message-ID: <008401cdbd8f$02e1fc30$08a5f490$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <001e01cdbd03$115f1d10$341d5730$@muller@ics-cnrs.unistra.fr>

  The current change doesn't work because the
whole checked out sources gets removed at the end of the
update-web-ari
not the end of the script, but the trap command, which is

~/ss % grep -n trap   update-web-ari
71:    trap "cd /tmp; rm -rf ${tmpdir}; exit" 0 1 2 15

  Should I modify ss/update-web-ari so that it
generate a temp-file that reports if the CVS sources
contain a contrib/ari/update-web-ari.sh file
and prevent tempdir deletion in that case?

  Any cleaner solution welcome,


  Pierre Muller


> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pierre Muller
> Envoyé : mercredi 7 novembre 2012 17:15
> À : 'Joel Brobecker'
> Cc : gdb-patches@sourceware.org; 'Tom Tromey'
> Objet : RE: [RFC] Create also ARI web page using CVS source in
> gdb/contrib/ari
> 
>   OK,
>   I committed the change to ss CVS directory,
> the gdbadmin ss directory is also update, which means that
> the first ari/test/index.html should be generated tonight.
> 
>   If anything goes wrong, you are going to get the email...
> If that happens, could you please forward it to me?
> 
> 
> 
> 
> > -----Message d'origine-----
> > De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> > owner@sourceware.org] De la part de Joel Brobecker
> > Envoyé : mercredi 7 novembre 2012 16:07
> > À : Pierre Muller
> > Cc : gdb-patches@sourceware.org; 'Tom Tromey'
> > Objet : Re: [RFC] Create also ARI web page using CVS source in
> > gdb/contrib/ari
> >
> > >   This is the purpose of the change below, after suggestions from
Joel.
> > > For now, it just adds a new directory on the sourceware.org web server
> > > http://sourceware.org/gdb/current/ari/test
> >
> > As said privately, it is fine to have a temporary staging area for
> > testing the new ARI scripts. In the interest of allowing you to make
> > progress a little faster, please feel free also to self-approve changes
> > that you feel confident about. (we're always quite happy to provide
> > feedback whenever you feel necessary, of course, and we will send
> > comments if there is something we notice).
> 
>   I will send a first bunch of fixes shortly...
> Mainly about ChangeLog formatting issues as usual...
> 
> Pierre



  parent reply	other threads:[~2012-11-08  8:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07  8:46 Pierre Muller
2012-11-07 15:07 ` Joel Brobecker
2012-11-07 16:15   ` Pierre Muller
2012-11-07 16:25     ` Joel Brobecker
2012-11-07 16:30       ` Pierre Muller
2012-11-08  8:57     ` Pierre Muller [this message]
2012-11-08 16:14       ` Joel Brobecker
2012-11-08 16:29         ` 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='008401cdbd8f$02e1fc30$08a5f490$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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