From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Fix fnchange.lst
Date: Sat, 19 Sep 2009 17:47:00 -0000 [thread overview]
Message-ID: <83ws3uvney.fsf@gnu.org> (raw)
In-Reply-To: <20090919155750.GU8910@adacore.com>
> Date: Sat, 19 Sep 2009 08:57:50 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > Would it be a good idea to run the ARI script when tarring a
> > pre-release or a release? Too many files were clashing after 8+3
> > truncation.
>
> I don't think that this _needs_ to be part of the release process.
> If we monitored the ARI results daily (I think that Pierre is doing
> that for us right now, but it looks like doschk checks are not included
> in the email), we shouldn't have this sort of issue.
While it's not fatal to have these issues exist on the trunk during
development, having them in a tarball is really bad. That's why I
won't even dream of insisting that ARE results are monitored daily.
But I do think we should re-check this before a tarball is released.
> If someone extracts out the script that does "dos checking" in
> the ARI script, and returns a textual list of files that cause
> problem, I don't mind adding it to the release procedure.
If Pierre can do that, fine. If not, if someone can tell me where do
I download the ARI script, I will give it a try.
Thanks.
next prev parent reply other threads:[~2009-09-19 17:47 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 [this message]
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
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=83ws3uvney.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