Hi All,

This should now be resolved.

Looks like we missed the replication config in the Gerrit migration
process. Sorry for the delay!

Regards,
Trevor Bramwell

On Thu, Jul 20, 2017 at 10:39:33AM +0200, Philippe Coval wrote:
> On 19/07/17 19:00, Morrow, Joseph L wrote:
> > Hi Phillipe,
> >
> > Can you try to ping the Helpdesk on this?
> Hi Joseph,
> I've been confirmed that this ticket is still open and under investigation
> by LF:
> 
> Reported as "IoTivity Helpdesk #43006 AutoReply: git unsync & jenkins
> health"
> 
> > It’s been a week and the issue is still unresolved.
> same for https://git.iotivity.org/iotivity/
> 
> > The Github for IoTivity actually says it hasn’t been touched in a month.
> Note, Do we have services relying on github mirror ?
> maybe it's safer to use upstream when fixed.
> 
> > This looks bad in a public facing way.
> IMHO, this issue should be public on our tracker,
> to prevent making false assumptions
> 
> > People should see that there is lots of activity there.
> or on tracker :)
> 
> Please track:
> https://jira.iotivity.org/browse/IOT-2279
> 
> If it helps I can update manually my private mirror,
> https://github.com/tizenteam/iotivity
> 
> > Thanks,
> Thank you for patience
> 
> -- 
> mailto:[email protected] gpg:0x467094BC
> https://blogs.s-osg.org/author/pcoval/
> 
> 
> _______________________________________________
> iotivity-dev mailing list
> [email protected]
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev

Attachment: binCVCC78O5Ab.bin
Description: application/rt-original-message

_______________________________________________
iotivity-dev mailing list
[email protected]
https://lists.iotivity.org/mailman/listinfo/iotivity-dev

Reply via email to