public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: overseers@gcc.gnu.org
Subject: Re: GCC 3.2.1 Core Tar Bzip2 ball MD5SUM mismatch (fwd)
Date: Thu, 09 Jan 2003 16:54:00 -0000	[thread overview]
Message-ID: <3E1DA935.7000908@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0301091058040.20078-100000@kern.srcf.societies.cam.ac.uk>

> I don't see any documentation at <http://sources.redhat.com/sourceware/>
> of how the md5.sum generation works, but I think problems such as this
> have been reported before.  Is there some locking mechanism the
> snapshot/release script can use to prevent generation of md5.sum while a
> snapshot/release is incompletely copied to the ftp directory?

Ah, so this is why the GDB snapshot process puts everything in a 
directory within ~ftp and then uses `mv' to put it in place.

I'll update GDB's release process to indicate the same.  Regardless of 
the md5 problem, using `cp' is bad.

thanks!

Andrew


      parent reply	other threads:[~2003-01-09 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 11:00 Joseph S. Myers
2003-01-09 14:21 ` Jason Molenda
2003-01-09 16:38 ` Christopher Faylor
2003-01-09 16:54 ` Andrew Cagney [this message]

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=3E1DA935.7000908@redhat.com \
    --to=ac131313@redhat.com \
    --cc=jsm28@cam.ac.uk \
    --cc=overseers@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).