From: Andrew Haley <aph@redhat.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: [patch] classpath merge 20121202
Date: Tue, 11 Dec 2012 17:23:00 -0000 [thread overview]
Message-ID: <50C76BEC.7060505@redhat.com> (raw)
In-Reply-To: <50BC8729.6090003@ubuntu.com>
On 12/03/2012 11:04 AM, Matthias Klose wrote:
> Prepared a classpath merge from classpath 20121202.
>
> - branches/CLASSPATH was updated to:
>
> - import classpath from git://git.savannah.gnu.org/classpath.git
> commit c814d82e5a435f93150cd28b7cf0f9d600ff400d
> - add m4/lib-{ld,link,prefix}.m4
>
> The additional m4 files were taken from the gettext sources,
> necessary to regenerate the auto* files.
>
> The merge itself didn't show up any issues. The testsuite doesn't show any
> regressions. Not attaching a diff of the regenerated header and class files.
> Ok for the trunk?
Yes. Unless anyone has any specific objections, I don't propose to
review the Classpath changes themselves because they've already
been reviewed.
Thanks,
Andrew.
next prev parent reply other threads:[~2012-12-11 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 11:04 Matthias Klose
2012-12-03 14:33 ` Andrew Hughes
2012-12-11 17:18 ` Matthias Klose
2012-12-11 17:23 ` Andrew Haley [this message]
2012-12-19 17:14 ` Matthias Klose
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=50C76BEC.7060505@redhat.com \
--to=aph@redhat.com \
--cc=doko@ubuntu.com \
--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).