Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Add scripts to generate ARI web pages to gdb/contrib/ari directory
Date: Fri, 25 May 2012 19:52:00 -0000	[thread overview]
Message-ID: <4FBFE2EF.2040807@redhat.com> (raw)
In-Reply-To: <4fb6d008.8727440a.10f3.1718SMTPIN_ADDED@mx.google.com>

On 05/18/2012 11:40 PM, Pierre Muller wrote:

>   Here is a RFA for inclusion of scripts to gdb/contrib/ari.
> 
>   The only changes to RFC-v2 are:
> 1) directory moved from gdb/ari to gdb/contrib./ari
> 2) create-web-ari-in-src.sh adapted to new directory
> 3) This script now output that location of the generated
> web page (with a different message depending on
> the existence of this file).


I really don't like the send_email thing.

> +    if [ "$send_email" == "true" ]; then
> +      if [ "${node}" = "sourceware.org" ]; then
> +	warning_email=gdb-patches@sourceware.org
> +      else
> +        # Use default email
> +	warning_email=${USER}@${node}
> +      fi

If the script really needs to know to send email, and where to send
it to, it'd be much much better to specify the destination with a
command line option.

As Joel said, we don't have to use the new gdb/ari scripts from ss
immediately. We can keep using the ones in ss until the gdb ones
are in shape.

Even sending unexpected email to ${USER}@${node} may not be a
good idea.  I'd vote for leaving the email sending off by default
until we have a command line option.

Other than that, it doesn't seem to cause anyone trouble to put
this stuff in, and work on top.

-- 
Pedro Alves


       reply	other threads:[~2012-05-25 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4fb6d008.8727440a.10f3.1718SMTPIN_ADDED@mx.google.com>
2012-05-25 19:52 ` Pedro Alves [this message]
2012-05-18 22:41 Pierre Muller
2012-05-25 19:47 ` Jan Kratochvil
2012-05-26  0:12 ` Sergio Durigan Junior

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=4FBFE2EF.2040807@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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