public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dodji Seketeli <dodji@redhat.com>
To: Andrew Hughes <ahughes@redhat.com>
Cc: Andrew Haley <aph@redhat.com>,
	GCJ-patches <java-patches@gcc.gnu.org>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, libjava] Use accessor functions to manipulate xmlOutputBuffer
Date: Thu, 09 Aug 2012 13:42:00 -0000	[thread overview]
Message-ID: <m3393ww5cb.fsf@redhat.com> (raw)
In-Reply-To: <1881397545.2449318.1344509333013.JavaMail.root@redhat.com>	(Andrew Hughes's message of "Thu, 9 Aug 2012 06:48:53 -0400 (EDT)")

Andrew Hughes <ahughes@redhat.com> writes:

>> OK.
>> 
>
> As this is a GNU Classpath change, it should go in there first to avoid creating
> a divergence which will cause later problems in merging.  Classpath is regularly
> merged into gcj as a whole.
>
> I found several patches during the last merge which had only been added to gcj
> (some without ChangeLog entries) and this slowed the process down considerably.
>
> Dodji, I can push this to Classpath on your behalf if you don't have commit
> access.

Oops.  I committed the patch before I saw your message.  Sorry.

If you agree, I can revert the commit so that you can commit it to
classpath then.  I don't think I have commit access to GNU classpath.

Sorry for the inconvenience.

-- 
		Dodji

  parent reply	other threads:[~2012-08-09 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3txwdvxyj.fsf@redhat.com>
2012-08-09  9:08 ` Andrew Haley
2012-08-09 10:49   ` Andrew Hughes
2012-08-09 12:00     ` Andrew Haley
2012-08-09 13:42     ` Dodji Seketeli [this message]
2012-08-09 14:40       ` Andrew Hughes
2012-08-09 15:02         ` Dodji Seketeli
2012-08-09 20:04           ` Andrew Hughes

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=m3393ww5cb.fsf@redhat.com \
    --to=dodji@redhat.com \
    --cc=ahughes@redhat.com \
    --cc=aph@redhat.com \
    --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).