From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Fix fnchange.lst
Date: Fri, 02 Oct 2009 11:43:00 -0000 [thread overview]
Message-ID: <83ske2ow90.fsf@gnu.org> (raw)
In-Reply-To: <20091001170107.GN10338@adacore.com>
> Date: Thu, 1 Oct 2009 10:01:07 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > Here you go. Save as "chkfnames" and invoke it like this:
> >
> > srcdir=FOO tmpdir=BAR ./chkfnames
>
> Can we make the script ignore libdecnumber and gnulib, .cvsignore
> files?
There are only a few of files in libdecnumber and gnulib, so I didn't
think it was justified to remove them. They do present a real
problem.
As for .cvsignore, they shouldn't present a problem because they are
not in the tarball. If you are running the script on the CVS sandbox,
then I guess we need to ignore them. I will see what I can do.
> Should we also skip testsuite files?
I don't think so. Any conflicts cause trouble when unpacking the
tarball on 8+3 and some older Windows systems.
> Right now, the script as is generates a lot of output about some things
> that we cannot fix in GDB itself. From a Q/A perspective, this is going
> to cause us to miss.
I agree that too much noise is bad, but do we really have a lot of
noise? How many positives are you willing to have before they are
noise?
> What should we do with the entries in section called:
> "The following resolve to the same SysV file names:"
Nothing. We don't care about this part of doschk's output. I thought
I made that section disappear, but it sounds like I goofed.
next prev parent reply other threads:[~2009-10-02 11:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 9:50 Eli Zaretskii
2009-09-19 15:58 ` Joel Brobecker
2009-09-19 17:47 ` Eli Zaretskii
2009-09-20 16:11 ` Joel Brobecker
2009-09-20 17:49 ` Eli Zaretskii
2009-09-20 19:48 ` Eli Zaretskii
2009-09-21 16:56 ` Joel Brobecker
2009-10-01 17:01 ` Joel Brobecker
2009-10-02 11:43 ` Eli Zaretskii [this message]
2009-10-02 15:25 ` 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=83ske2ow90.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--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