Open Stack

IIRC it's an issue with search index, that should be rebuilded, but we
don't sure that it could be done while gerrit online, so, I think
it'll be discussed and fixed later.

On Mon, May 26, 2014 at 2:49 PM, Alexander Tivelkov
<ativelkov at mirantis.com> wrote:
> Hi folks,
>
> After the "murano-api" repo was renamed to "murano", all the old changesets
> in gerrit for this repository are missing in all the queries:
> "https://review.openstack.org/#/q/project:stackforge/murano,n,z" returns
> only new (or recently updated) changesets, while
> "https://review.openstack.org/#/q/project:stackforge/murano-api,n,z" does
> not return anything at all. Even the currently open (i.e. not merged)
> changesets are not shown.
>
> Direct links to the changesets still work, and once rebased to a new repo
> the changeset becomes visible, however all the history seems lost.
> Previously, if I was looking for the reasons behind some line of code, I
> could git-annotate the code, find the commit message and use the gerrit
> change-id from that message to locate the change in gerrit. Not it seems
> impossible.
>
> Is there any way to recover the old changesets?
>
> --
> Regards,
> Alexander Tivelkov
>
>
> On Sat, May 24, 2014 at 2:58 AM, James E. Blair <jeblair at openstack.org>
> wrote:
>>
>> jeblair at openstack.org (James E. Blair) writes:
>>
>> > Hi,
>> >
>> > On Friday, May 23 at 21:00 UTC Gerrit will be unavailable for about 20
>> > minutes while we rename some projects.  Existing reviews, project
>> > watches, etc, should all be carried over.
>>
>> This is complete.  The actual list of renamed projects is:
>>
>>     stackforge/barbican -> openstack/barbican
>>     openstack/oslo.test -> openstack/oslotest
>>     openstack-dev/openstack-qa -> openstack-attic/openstack-qa
>>     openstack/melange -> openstack-attic/melange
>>     openstack/python-melangeclient -> openstack-attic/python-melangeclient
>>     openstack/openstack-chef -> openstack-attic/openstack-chef
>>     openstack/database-api -> openstack-attic/database-api
>>     stackforge/climate -> stackforge/blazar
>>     stackforge/climate-nova -> stackforge/blazar-nova
>>     stackforge/python-climateclient -> stackforge/python-blazarclient
>>     stackforge/murano-api -> stackforge/murano
>>     openstack/baremetal-specs -> openstack/ironic-specs
>>     openstack/object-specs -> openstack/swift-specs
>>     openstack/orchestration-specs -> openstack/heat-specs
>>     openstack/identity-specs -> openstack/keystone-specs
>>     openstack/telemetry-specs -> openstack/ceilometer-specs
>>
>> The consensus about specs repo names seemed to be converging on
>> 'codename' significantly enough that we felt it would be best to drop
>> the previous plan to rename to program name, and instead rename the
>> handful of brand-new repos that had been created to their codenames.
>> Giving that kind of notice isn't our favorite thing to do, to put it
>> mildly, but I think this is for the best and we can get back to actually
>> writing specs now.  And maybe code.
>>
>> Thanks to Sergey, Monty, Clark and Jeremy all of whom did a great deal
>> of work on this.
>>
>> -Jim
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Sincerely yours,
Sergey Lukjanov
Sahara Technical Lead
(OpenStack Data Processing)
Mirantis Inc.