I didn't do anything to it. I think it was just a delay on propagating the
changes from apache git to github mirror.
- Sijie
On Wed, Jun 14, 2017 at 9:52 AM, Jia Zhai wrote:
> That's great, Thanks Sijie.
> How is this happen, and Is there anything that we could do to avoid it? :)
>
> On Wed, Ju
That's great, Thanks Sijie.
How is this happen, and Is there anything that we could do to avoid it? :)
On Wed, Jun 14, 2017 at 1:58 AM, Enrico Olivelli
wrote:
> Now I see on apache git repo this sha
> 07852d35856dca232450135913090bac27b29abe and on github the same
> 07852d35856dca232450135913090
Now I see on apache git repo this sha
07852d35856dca232450135913090bac27b29abe and on github the same
07852d35856dca232450135913090bac27b29abe
Thank you Sijie
-- Enrico
2017-06-12 21:49 GMT+02:00 Sijie Guo :
> It seems that the recent merged changes are not propagated into the github
> mirror. it