On 2019-10-15 11:29:16 -0500 (-0500), Dean Troyer wrote:
On Tue, Oct 15, 2019 at 11:17 AM Saul Wold <sgw@linux.intel.com> wrote:
I am wondering if it would be easier to test and review this if we had all these changes on a branch and have an associated manifest.
You do not need branches to do that, repo knows how to pick specific reviews out of Gerrit to build its tree. You don't even need to merge the manifest, just propose a review with it and everyone can pull that directly.
I've often likened Gerrit to a solution for sharing lightweight, ephemeral topic branches. It works well for that purpose. We also replicate all Gerrit change refs (and associated Git notes) to the https://opendev.org/ Gitea service, so you can do things like: git clone https://opendev.org/starlingx/manifest cd manifest git fetch origin refs/changes/00/687200/1 git checkout -B stx_dashboard_train FETCH_HEAD ...or cherry-pick, or merge, or rebase, and never even have to communicate with the Gerrit server at all (as long as the change and patchset numbers are already known). Note that with checkout in particular, you'll automatically pick up any parent changes too if they're already in series. -- Jeremy Stanley