From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] First scripts for ARI support inisde gdb tree
Date: Fri, 18 May 2012 13:48:00 -0000 [thread overview]
Message-ID: <87wr49iori.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120517203915.GH10253@adacore.com> (Joel Brobecker's message of "Thu, 17 May 2012 13:39:15 -0700")
>> Ultimately what I would like is for 'make check' to die if we violate
>> some rule.
Joel> Interesting idea. We'd have to record a baseline, I assume.
Since it is working on the source, which is the same everywhere, I think
we can adopt a "zero fail" rule. For example perhaps whatever
exceptions there are to the rules could be marked in the source.
That's just speculation though. I haven't looked at the ARI scripts.
Tom
next prev parent reply other threads:[~2012-05-18 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 22:25 Pierre Muller
2012-05-17 13:16 ` Joel Brobecker
2012-05-17 19:46 ` Tom Tromey
2012-05-17 20:39 ` Joel Brobecker
2012-05-18 13:48 ` Tom Tromey [this message]
2012-05-18 17:26 ` Joel Brobecker
2012-05-18 8:25 ` [RFC-v2] " Pierre Muller
2012-05-18 13:03 ` Joel Brobecker
2012-05-17 17:29 ` [RFC] " 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=87wr49iori.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.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