You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@distributedlog.apache.org by Sijie Guo <gu...@gmail.com> on 2017/06/12 19:49:41 UTC
Github repo isn't in-sync with the git repo
It seems that the recent merged changes are not propagated into the github
mirror. it seems something is broken in INFRA. try to asking INFRA team.
Re: Github repo isn't in-sync with the git repo
Posted by Henry Saputra <he...@gmail.com>.
This is happening once a while due to lag of sync from ASF repo and Github
mirror =(
- Henry
On Wed, Jun 14, 2017 at 11:06 AM, Sijie Guo <gu...@gmail.com> wrote:
> 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 <zh...@gmail.com> wrote:
>
> > 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 <eo...@gmail.com>
> > wrote:
> >
> > > 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 <gu...@gmail.com>:
> > > > It seems that the recent merged changes are not propagated into the
> > > github
> > > > mirror. it seems something is broken in INFRA. try to asking INFRA
> > team.
> > >
> >
>
Re: Github repo isn't in-sync with the git repo
Posted by Sijie Guo <gu...@gmail.com>.
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 <zh...@gmail.com> wrote:
> 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 <eo...@gmail.com>
> wrote:
>
> > 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 <gu...@gmail.com>:
> > > It seems that the recent merged changes are not propagated into the
> > github
> > > mirror. it seems something is broken in INFRA. try to asking INFRA
> team.
> >
>
Re: Github repo isn't in-sync with the git repo
Posted by Jia Zhai <zh...@gmail.com>.
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 <eo...@gmail.com>
wrote:
> 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 <gu...@gmail.com>:
> > It seems that the recent merged changes are not propagated into the
> github
> > mirror. it seems something is broken in INFRA. try to asking INFRA team.
>
Re: Github repo isn't in-sync with the git repo
Posted by Enrico Olivelli <eo...@gmail.com>.
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 <gu...@gmail.com>:
> It seems that the recent merged changes are not propagated into the github
> mirror. it seems something is broken in INFRA. try to asking INFRA team.