Thanks, will do.
From: <keti-dev-bounces@xxxxxxxxxxx> on behalf of Benjamin Cabé <benjamin.cabe@xxxxxxxxxxxxxxxxxxxxxx>
Reply-To: keti developer discussions <keti-dev@xxxxxxxxxxx>
Date: Monday, January 15, 2018 at 8:56 AM
To: "keti-dev@xxxxxxxxxxx" <keti-dev@xxxxxxxxxxx>
Subject: EXT: Re: [keti-dev] Keti initial contribution - git repo
BTW, may I suggest that someone from the team posts on the
iot-wg@xxxxxxxxxxx mailing list to announce that the code for Keti is finally available? I know many people that will be interested in hearing this :-)
Congratulations once again,
Benjamin -
Le 12 janv. 2018 à 19:11, Chopra, Sanjeev (GE Digital) <chopra@xxxxxx> a écrit :
Benjamin, we decided to apply the package name changes directly on keti/eclipse – so should be done sometime next week. Next, we want to setup the CI loop to enable validation of any changes on the repo and publishing
of snapshots/releases.
I’m following up on Anubhav’s request on IPzilla here on the mailing list, as this is information that might be useful for others.
"I've checked in our code to
we don't have permission to force-push to the master branch so I had to resort
to adding another commit on top of the initial one by the webmaster. I was
attempting to follow instructions similar to what's described in
mirroring process in the Eclipse docs beyond what's covered in
the actual process for mirroring to our repo under the eclipse public GitHub
As far as getting the actual Keti code contributed to https://github.com/eclipse/keti,
which is the repo for the code, have all the Keti committers filled in their Github ID in the eclipse portal? This is how webmaster can provide write access to the commiter's Github accounts.
Benjamin Cabé – IoT Program Manager & Evangelist
Eclipse Foundation
+33 (0) 619196101
@kartben
|