public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: Doug Evans <dje@google.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [RFA 7/8] validate_failures.py: New options --manifest_subdir, --manifest_name
Date: Fri, 30 Nov 2012 14:46:00 -0000	[thread overview]
Message-ID: <CAD_=9DRsazPFmH5HZf-_NL66crcng3xgx1GGhLxsGX7wz6JuxA@mail.gmail.com> (raw)
In-Reply-To: <20663.60390.66132.570663@ruffy2.mtv.corp.google.com>

On Thu, Nov 29, 2012 at 6:12 PM, Doug Evans <dje@google.com> wrote:
> Diego Novillo writes:
>  > On Sat, Nov 24, 2012 at 5:58 PM, Doug Evans <dje@google.com> wrote:
>  > > Hi.
>  > > This seventh patch adds new options --manifest_subdir, --manifest_name.
>  > > Useful when using validate_failures.py with a different tool, instead of gcc.
>  > >
>  > > Ok to check in?
>  > >
>  > > 2012-11-24  Doug Evans  <dje@google.com>
>  > >
>  > >         * testsuite-management/validate_failures.py: New options --manifest_subdir,
>  > >         --manifest_name.
>  >
>  > OK.
>
> This is another baby-steps kinda patch.
> Instead of adding --manifest_{subdir,name},
> this patch just parameterizes the gcc-specific manifest subdir,
> and provides a utility to compute the manifest path.
>
> Ok to check in?
>
> 2012-11-29  Doug Evans  <dje@google.com>
>
>         * testsuite-management/validate_failures.py: Add function
>         GetManifestPath.  New global _MANIFEST_SUBDIR.

OK.


Diego.

      reply	other threads:[~2012-11-30 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-24 22:59 Doug Evans
2012-11-25 15:43 ` Diego Novillo
2012-11-30  0:32   ` Doug Evans
2012-11-30 14:46     ` Diego Novillo [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='CAD_=9DRsazPFmH5HZf-_NL66crcng3xgx1GGhLxsGX7wz6JuxA@mail.gmail.com' \
    --to=dnovillo@google.com \
    --cc=dje@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).