move libweave back to chromium-review gerrit |
||
Issue descriptionForked from email thread. In the chromiumos checkout repo src/weave/libweave is the only remaining git repo we have in our manifest that references the weave remote. This extra gerrit instance causes occasional authentication issues for developers, and since development there is not active this is complexity for no gain. Let's move this back to chromium-review
,
Feb 24 2017
,
May 4 2017
So, what I think we can do here is: 1. Create a new repo weave/libweave in https://chromium-review.googlesource.com 2. Fill in this repo with the current content of the remote repo we are using today. 3. Modify the manifest to point at the new repo instead of the old repo (I _think_ this will just work, but if not we may need to do some hacky libweave2 or some such to migrate). l SG?
,
May 4 2017
if you have the cycles, please migrate :) i would have suggested just moving libweave under existing chromiumos/ namespaces since we own it now (libweave is dead upstream), but looks like you already created it.
,
May 4 2017
Hopefully, this won't be around for too much longer, so I don't expect it to matter so much :P
,
May 5 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/manifest-internal/+/19672f0b18911fcb7f6b67b75c7d8e97bc73ceba commit 19672f0b18911fcb7f6b67b75c7d8e97bc73ceba Author: Eric Caruso <ejcaruso@google.com> Date: Fri May 05 21:42:46 2017
,
May 10 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by akes...@chromium.org
, Jan 9 2017Owner: ejcaruso@chromium.org