This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [commit] Fix fnchange.lst
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 19 Sep 2009 20:45:25 +0300
- Subject: Re: [commit] Fix fnchange.lst
- References: <831vm3w9ic.fsf@gnu.org> <20090919155750.GU8910@adacore.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.