From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Daniel Jacobowitz'" <drow@false.org>,
"'Eli Zaretskii'" <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFA] gdb_ari.sh changes to discard some file types for specific tests
Date: Thu, 25 Oct 2007 07:22:00 -0000 [thread overview]
Message-ID: <002d01c816d7$29728590$7c5790b0$@u-strasbg.fr> (raw)
In-Reply-To: <20071024202518.GM10943@caradoc.them.org>
Thanks!
I have more changes, especially
related to doscheck.c
(which is not used on the web pages,
but probably should be enabled again.)
I changed the output of doscheck to
avoid getting false duplicates for files
in different directories.
The next question is for Eli, as DJGPP maintainer:
I have locally a working version of doscheck,
which avoid duplicates in different directories,
but still reveals some conflicts for DJGPP.
The most notable is
gdb/ChangeLog and gdb/ChangeLog-2006
but there are others in bfd, libdecnumber, gdb/testsuite
and other directories,
but lots of these duplicates are probably
in directories that are not even put in
the DJGPP gdb sources.
Should I send the whole list,
or should we start by updating the
directory exclusion list in update_web_ari?
By the way, is the script that
generates the DJGPP gdb source public?
If yes, where can I find it?
Pierre
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of 'Daniel Jacobowitz'
> Sent: Wednesday, October 24, 2007 10:25 PM
> To: Pierre Muller
> Cc: gdb-patches@sourceware.org
> Subject: Re: [RFA] gdb_ari.sh changes to discard some file types for
> specific tests
>
> On Tue, Oct 16, 2007 at 02:41:34PM +0200, Pierre Muller wrote:
> > UCASE and EditCase tests are currently polluted
> > by lex and yacc files.
> > This patch discards those bugs if the source
> > is a lex or yacc source.
> > The patch also contains the fixes for xasprintf and xvasprintf
> > that I already proposed yesterday.
> >
> > I am new to AWK scripts,
> > so I am unsure if my changes are
> > standard.
> >
> > Is this OK?
>
> I checked in something similar - we shouldn't be looking at lex/yacc
> output files at all.
>
> --
> Daniel Jacobowitz
> CodeSourcery
next prev parent reply other threads:[~2007-10-25 7:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 13:56 Pierre Muller
2007-10-24 20:29 ` 'Daniel Jacobowitz'
2007-10-25 7:22 ` Pierre Muller [this message]
2007-10-25 13:23 ` 'Daniel Jacobowitz'
2007-10-25 21:55 ` Eli Zaretskii
2007-10-25 22:10 ` Eli Zaretskii
2007-10-26 7:44 ` Pierre Muller
2007-10-26 9:44 ` Eli Zaretskii
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='002d01c816d7$29728590$7c5790b0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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