<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">… and where is upstream for EAP-6.x ?<div><br></div><div>I think it is <a href="https://github.com/jbossas/jboss-eap">jboss-eap/6.x</a>, and not <a href="https://github.com/jbossas/jboss-as/tree/7.1">jboss-as/7.1</a><br><div><br><div><div>On Apr 17, 2013, at 1:04 PM, Heiko Braun <<a href="mailto:hbraun@redhat.com">hbraun@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><br></div><div>If the patch needs to be upstream first, the upstream build can be used to verified it, no?</div><div><br></div><div><br></div><br><div><div>On Apr 17, 2013, at 1:02 PM, Thomas Diesler <<a href="mailto:thomas.diesler@jboss.com">thomas.diesler@jboss.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">All would be good if the reporter can verify the patch before it goes in the next EAP release, can he?</span></blockquote></div><br></div></blockquote></div><br><div>
<div><pre class="moz-signature" cols="72">xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx </pre><div><br></div></div><br class="Apple-interchange-newline">
</div>
<br></div></div></body></html>