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 16:29:00 -0000 [thread overview]
Message-ID: <000901cdbdce$3f6552d0$be2ff870$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20121108161415.GL5103@adacore.com>
I finally managed to generate a web page:
http://sourceware.org/gdb/current/ari/test/
I just left the data corresponding to the
extraction of the tarball in place,
but I don't think that the data will grow,
as the nightly script contains some code that
clean the temp dir at a higher level.
Pierre
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : jeudi 8 novembre 2012 17:14
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org; 'Tom Tromey'
> Objet : Re: [RFC] Create also ARI web page using CVS source in
> gdb/contrib/ari
>
> Hi Pierre,
>
> > 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?
>
> What I would probably do is perform the ARI generation in a non-temporary
> directory of our choosing. I don't think we should turn the cleanup off,
> because we'll start leaving a lot of data behind each day.
>
> --
> Joel
prev parent reply other threads:[~2012-11-08 16:29 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
2012-11-08 16:14 ` Joel Brobecker
2012-11-08 16:29 ` 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='000901cdbdce$3f6552d0$be2ff870$@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