Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] Change OK: to ARI: for ARI rule ignore
Date: Thu, 23 Apr 2009 06:51:00 -0000	[thread overview]
Message-ID: <002a01c9c3df$d77f5760$867e0620$@u-strasbg.fr> (raw)
In-Reply-To: <m3ab68tfta.fsf@fleche.redhat.com>



> -----Message d'origine-----
> De : Tom Tromey [mailto:tromey@redhat.com]
> Envoyé : Thursday, April 23, 2009 1:44 AM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFC] Change OK: to ARI: for ARI rule ignore
> 
> >>>>> "Pierre" == Pierre Muller <muller@ics.u-strasbg.fr> writes:
> 
> Pierre>   Thus, I would like to restrict that rule to only accept
> Pierre> /* ARI: rule_name */.
> 
> I think this sounds like a good idea.

  
> Pierre>   The main problem if I commit both before next release is
> that,
> Pierre> if ARI is rerun on gdb 6.8 release, this change will generate
> Pierre> new false warnings.
> 
> Is that something we would want to do?  Can't we just run it once, say
> today, and save the results?  I mean, if that is something we need.

You are right, the ARI page for 6.8 release dates
from 2008/03/27 which is the release date...
There is nothing in the automatic script that seems to update
this page, so maybe I can commit both together?

Pierre


  reply	other threads:[~2009-04-23  6:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 22:27 Pierre Muller
2009-04-22 23:44 ` Tom Tromey
2009-04-23  6:51   ` Pierre Muller [this message]
2009-04-23 18:19     ` Tom Tromey
2009-04-24 23:26       ` Pierre Muller
2009-04-28 13:09         ` Daniel Jacobowitz
2009-05-01  8:18         ` Pierre Muller
2009-05-06 16:15           ` Joel Brobecker
2009-05-06 16:26             ` Pierre Muller
2009-04-23 16:42   ` Joel Brobecker

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='002a01c9c3df$d77f5760$867e0620$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --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