From: David Huggins-Daines <dhd@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] GCC 2.96 merge complete (I hope)
Date: 07 Jul 2000 22:12:48 -0400 [thread overview]
Message-ID: <87d7kpe5en.fsf@linuxcare.com> (raw)
Okay, the merge of p.e.h.c's gcc module to current 2.96 is complete,
modulo things that may have slipped through the cracks due to CVS
being stupid.
As mentioned in the previous message, the old stuff is on the
'gcc-2_9-hppa-20000707' branch tag if you care to look at it.
We now also have a 'GNU_DIST' vendor branch which is intended to be
used to track the mainline GCC tree. So, nice diffs can now be
obtained by running 'cvs rdiff -u -r GNU_DIST -r HEAD gcc'.
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
reply other threads:[~2000-07-08 2:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87d7kpe5en.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=parisc-linux@thepuffingroup.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.