From: Matthias Klose <doko@cs.tu-berlin.de>
To: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: merging classpath-0.97.2 into trunk
Date: Thu, 26 Jun 2008 23:18:00 -0000 [thread overview]
Message-ID: <18532.9129.695806.812344@gargle.gargle.HOWL> (raw)
I'd like to merge classpath-0.97.2 into trunk. The merge is currently
prepared on branches/gcj/classpath-0961-import-branch. The branch
doesn't show regressions on the libjava and the mauve testsuites, both
configured with and without --enable-java-maintainer-mode. The merge
was ok'd by Tom Tromey [1] with the constraint to not conflict with
another major merge into trunk. I'd like to do this merge this
weekend, if no other major merge is pending. Please consider the
libjava directory as (informally) frozen until this merge is done.
This merge doesn't add much new code, but another merge of
classpath-0.98 (adding the gjdoc code) is likely before 4.4 branches.
Matthias
[1] http://gcc.gnu.org/ml/java-patches/2008-q2/msg00029.html
next reply other threads:[~2008-06-26 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 23:18 Matthias Klose [this message]
2008-06-28 13:44 ` Matthias Klose
2008-07-07 18:32 ` Tom Tromey
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=18532.9129.695806.812344@gargle.gargle.HOWL \
--to=doko@cs.tu-berlin.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@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).