Well, so as long as the Tee, and the authors of these reviews (if different), and any other interested parties are all aware of the forthcoming history rewrite, I won't object. The interested community should be small for such a new repo. Scott On 2019-06-14 9:05 p.m., Penney, Don wrote:
I see the following: 2dc3228 Add .gitignore to ansible-stx-playbooks repo d3360f6 Populate stx-ansible-playbooks repo 6bef82a Initial zuul / TOX setup 4266117 Added .gitreview
The second one on the list, d3360f6, was just moving the playbookconfig dir from stx-config, and population the centos_iso_image.inc and centos_pkg_dirs files for the build. I believe the first and second ones were also just copies of the files in stx-config, setting up the repo.
-----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Friday, June 14, 2019 8:16 PM To: Jeremy Stanley Cc: starlingx Subject: Re: [Starlingx-discuss] Bootstrap playbook relocation
On Fri, Jun 14, 2019 at 6:44 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
Once you have an external, publicly cloneable repo somewhere from which I can pull the new refs, I'm happy push --force those over top of the old content. Or if you prefer, you can propose a temporary ACL change for that repo in openstack/project-config to grant some Gerrit group you're in access to do the same, and I'll be glad to review/approve it. Thanks Jeremy, I imagine we'll create it in starlingx-staging and push from there. It sounds like we'll see what Scott wants to do on Monday.
There are 4 merged reviews in that project now, I know we'll have to re-create them. After a force-push will they still have anything interesting? I don't think it will be a big deal, just curious.
dt