When I originally wanted to create the naming for glance_store to be
consistent across platforms, we already had the library glance_store out
(actually it first called glance.store but due to the anxiety of
namespace conflicts it was quickly renamed to glance_store in git/gerrit
etc.). Creating a
Yes, that is why I have suggested you either update the mapping so it is
correct or you use glance which is what the mapping currently says you
want to use.
On Thu, Nov 19, 2015, at 12:08 PM, Nikhil Komawar wrote:
> When I originally wanted to create the naming for glance_store to be
> consistent
On 11/19/2015 11:38 AM, Clark Boylan wrote:
On Thu, Nov 19, 2015, at 08:00 AM, Matt Riedemann wrote:
Patches in Gerrit aren't syncing status to the glance-store project in
launchpad b/c the project in launchpad is called glance-store and in git
it's glance_store.
Looking at the project
Patches in Gerrit aren't syncing status to the glance-store project in
launchpad b/c the project in launchpad is called glance-store and in git
it's glance_store.
Looking at the project creators guide it says to specify a group for the
mapping [1] to fix this but glance_store in projects.yaml
On 11/19/15, 10:00, "Matt Riedemann" wrote:
>Patches in Gerrit aren't syncing status to the glance-store project in
>launchpad b/c the project in launchpad is called glance-store and in git
>it's glance_store.
>
>Looking at the project creators guide it says to
On Thu, Nov 19, 2015, at 08:00 AM, Matt Riedemann wrote:
> Patches in Gerrit aren't syncing status to the glance-store project in
> launchpad b/c the project in launchpad is called glance-store and in git
> it's glance_store.
>
> Looking at the project creators guide it says to specify a group