Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Fix fnchange.lst
Date: Sat, 19 Sep 2009 15:58:00 -0000	[thread overview]
Message-ID: <20090919155750.GU8910@adacore.com> (raw)
In-Reply-To: <831vm3w9ic.fsf@gnu.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. In the meantime,
we can just make sure we check the ARI on the web just before we cut
the branch, and maybe just before we create the release tarball.

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.

-- 
Joel


  reply	other threads:[~2009-09-19 15:58 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 [this message]
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
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=20090919155750.GU8910@adacore.com \
    --to=brobecker@adacore.com \
    --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