Yes, it's most likely because 5.2.x is identical to master at this point.

Cheers
Dan


On Mon, Feb 4, 2013 at 12:17 PM, Galder Zamarreño <galder@redhat.com> wrote:
Something's wrong here because whereas 5.1.x and previous branches appear as "unmerged", 5.2.x appears as "merged branch"

Maybe the issue is due to the fact that no different commits have been pushed to 5.2.x yet…

Cheers,

On Feb 4, 2013, at 11:11 AM, Galder Zamarreño <galder@redhat.com> wrote:

> Hey Mircea,
>
> Seems like there's no 5.2.x branch in Infinispan upstream:
> https://github.com/infinispan/infinispan/branches
>
> Did you forgot to push when you branched? Or is there any other issue?
>
> Cheers,
> --
> Galder Zamarreño
> galder@redhat.com
> twitter.com/galderz
>
> Project Lead, Escalante
> http://escalante.io
>
> Engineer, Infinispan
> http://infinispan.org
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev


--
Galder Zamarreño
galder@redhat.com
twitter.com/galderz

Project Lead, Escalante
http://escalante.io

Engineer, Infinispan
http://infinispan.org


_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev