Hi Thanks for your reply. Unfortunately the problem is still there. Looking at:
https://github.com/apache/camel/commits/trunk It claims that the latest commit on the trunk would be 8 days old however that's not really true if you would look at: https://git-wip-us.apache.org/repos/asf/camel.git That's all the commits of the last days we did on https://git-wip-us.apache.org/repos/asf/camel.git are MISSING on the GitHub read-only mirror https://github.com/apache/camel Any idea what the problem could be? Babak PS: I've also put the Camel development Mailing list into the Cc: of this reply. Am 09.05.13 08:30 schrieb "Ryan Tomayko (GitHub Staff)" unter <supp...@github.com>: >It looks like the repository on github.com is in sync with both >git://git.apache.org/camel.git and >https://git-wip-us.apache.org/repos/asf/camel.git. The default branch is >set to trunk: > > $ git ls-remote https://git-wip-us.apache.org/repos/asf/camel.git | >grep trunk > b4f6a8f6dcbe1009a2274bf94429d1d655ecba79 >refs/original/refs/remotes/trunk > 83231e190735e435c634822893eddbd0b0480c0c >refs/original/refs/remotes/trunk@735814 > b0ccd947445df66a980034bb87f3fdbdb8066d02 refs/remotes/trunk > ad3c7d447e4cba0f68d83e3bc0b9d75ee1e978f5 >refs/remotes/trunk@735814 > $ git ls-remote git://git.apache.org/camel.git | grep trunk > b0ccd947445df66a980034bb87f3fdbdb8066d02 refs/heads/trunk > b4f6a8f6dcbe1009a2274bf94429d1d655ecba79 >refs/original/refs/remotes/trunk > 83231e190735e435c634822893eddbd0b0480c0c >refs/original/refs/remotes/trunk@735814 > b0ccd947445df66a980034bb87f3fdbdb8066d02 refs/remotes/trunk > ad3c7d447e4cba0f68d83e3bc0b9d75ee1e978f5 >refs/remotes/trunk@735814 > $ git ls-remote https://github.com/apache/camel.git | grep trunk > b0ccd947445df66a980034bb87f3fdbdb8066d02 refs/heads/trunk > b4f6a8f6dcbe1009a2274bf94429d1d655ecba79 >refs/original/refs/remotes/trunk > 83231e190735e435c634822893eddbd0b0480c0c >refs/original/refs/remotes/trunk@735814 > b0ccd947445df66a980034bb87f3fdbdb8066d02 refs/remotes/trunk > ad3c7d447e4cba0f68d83e3bc0b9d75ee1e978f5 >refs/remotes/trunk@735814 > >Did this end up fixing itself or was there something specific on the site >that looked wrong?