[jboss-as7-dev] OSGi blocker should be resolved
Thomas Diesler
thomas.diesler at jboss.com
Tue Sep 18 15:34:15 EDT 2012
I rebased on the previous master commit - that fixed it too.
On 09/18/2012 09:15 PM, Thomas Diesler wrote:
> I know it should not, but if you look at the sha1 values in
>
> https://github.com/jbossas/jboss-as/pull/2992/commits
>
> you'll see that my commits are a fast forward on the current master.
> I've seen this before and AFAIR it goes away when I rebase on the next
> commit to master.
>
> On 09/18/2012 04:05 PM, David M. Lloyd wrote:
>> On 09/18/2012 09:04 AM, Thomas Diesler wrote:
>>> PS: For some PRs GitHub lists commits that are already in master, which
>>> makes it difficult to see the real diff.
>> It should not do this if you're properly rebased. Chances are if it's
>> showing already-merged commits then a merge cannot happen cleanly and a
>> rebase/cleanup is needed anyway.
>>
>>
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
More information about the jboss-as7-dev
mailing list