Hi,
I'm going to do the trunk to redhat/gcc-4_1-branch backport now. I'm planning to tag revision 116352 as "redhat-java-merge-20060823". If you have an outstanding patch that you want included in this merge, let me know today and I'll hold off tagging until you've committed it.
Tom
Thomas Fitzsimmons wrote:
Hi,
I'm going to do the trunk to redhat/gcc-4_1-branch backport now. I'm planning to tag revision 116352 as "redhat-java-merge-20060823".
Make that: "redhat/4_1-branch-java-merge-20060823".
If you have an outstanding patch that you want included in this merge, let me know today and I'll hold off tagging until you've committed it.
Tom
-- fedora-devel-java-list mailing list fedora-devel-java-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-java-list
"Tom" == Thomas Fitzsimmons fitzsim@redhat.com writes:
Tom> I'm going to do the trunk to redhat/gcc-4_1-branch backport now. I'm Tom> planning to tag revision 116352 as "redhat-java-merge-20060823". If Tom> you have an outstanding patch that you want included in this merge, Tom> let me know today and I'll hold off tagging until you've committed it.
There's the libgcj_bc patch I sent last night. But ... it is ok if you push forward with the merge; we can merge this patch in separately easily enough. It is still waiting for a bit of review.
Tom
java-devel@lists.fedoraproject.org