From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Andreas Schwab <schwab@suse.de>
Cc: <gcc@gcc.gnu.org>
Subject: Re: gcc-ss-20011203 is now available
Date: Tue, 04 Dec 2001 07:59:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0112041556420.14880-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <jevgfnm351.fsf@sykes.suse.de>
On 4 Dec 2001, Andreas Schwab wrote:
> gccadmin@sources.redhat.com writes:
>
> |> gcc-ss-20011203 is now available on
> |> ftp://gcc.gnu.org/pub/gcc/snapshots/2001-12-03
> |> and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
>
> Seems like the snapshot has been made in the middle of a checkin, because
> ia64 does not build due to missing "prefetch" rtx code.
In the middle of a series of 19 checkins, you mean. Could people please
ensure that they commit each logical patch (such that users should not try
to build an intermediate state) in a single commit with all relevant files
named on the command line?
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2001-12-04 15:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 19:13 gccadmin
2001-12-04 7:11 ` Andreas Schwab
2001-12-04 7:59 ` Joseph S. Myers [this message]
2001-12-04 12:16 ` guerby
2001-12-04 12:24 ` Joseph S. Myers
2001-12-04 12:30 ` Phil Edwards
2001-12-04 12:36 ` Joseph S. Myers
2001-12-04 12:46 ` Phil Edwards
2001-12-04 12:50 ` Assembly in Gcc Mark Cuss
2001-12-04 13:03 ` Graham Stott
2001-12-04 13:27 ` Mark Cuss
2001-12-04 19:00 ` Tim Prince
2001-12-11 11:14 ` Embedded Assembly and MMX in GCC Mark Cuss
2001-12-11 12:35 ` Alexandre Oliva
2001-12-11 13:00 ` Mark Cuss
2001-12-11 13:18 ` Alexandre Oliva
2001-12-11 14:09 ` Mark Cuss
2001-12-12 3:48 ` Andreas Schwab
2001-12-11 14:38 ` Craig Rodrigues
2001-12-04 19:54 ` gcc-ss-20011203 is now available Mark Mitchell
2001-12-04 8:17 Richard Kenner
2001-12-04 8:32 ` Andreas Schwab
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=Pine.LNX.4.33.0112041556420.14880-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=schwab@suse.de \
/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).