<div dir="auto"><div><div class="gmail_extra"><div class="gmail_quote">On 7 Sep 2017 6:25 pm, "Niels de Vos" <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="quoted-text">On Thu, Sep 07, 2017 at 04:41:54PM +0530, Nigel Babu wrote:<br>
> On Thu, Sep 07, 2017 at 12:43:28PM +0200, Niels de Vos wrote:<br>
> ><br>
> > Q: Can patches of a series be merged before all patches in the series<br>
> > have a +2? Initial changes that prepare things, or add new (unused) core<br>
> > functionalities should be mergable so that follow-up patches can be<br>
> > posted against the HEAD of the branch.<br>
> ><br>
> > A: Nigel?<br>
> ><br>
><br>
> If you have patches that are dependent like this:<br>
><br>
> A -> B -> C -> D<br>
><br>
> where A is the first patch and B is based on top of A and so forth.<br>
><br>
> Merging A is not dependent on B. It can be merged any time you have Code Review<br>
> and Regression votes.<br>
><br>
> However, you cannot merge B until A is ready or merged. If A is unmerged, but<br>
> is ready to merge, when you merge B, Gerrit will merge them in order, i.e.<br>
> first merge A, and B automatically.<br>
><br>
> Does this answer your question? If it helps, I can arrange for staging to be<br>
> online so moe people can test this out.<br>
<br>
</div>That answers my question, I don't need to try it out myself.<br>
<br>
Thanks!<br>
<font color="#888888">Niels<br>
</font><div class="elided-text">______________________________<wbr>_________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><span style="font-family:sans-serif">Gerrit still provides all the meta information about patches in a special branch as git-notes. Git can be configured to display these notes along with commit messages. You would still effectively get the same experience as before.</span><div dir="auto" style="font-family:sans-serif"><br></div><div dir="auto" style="font-family:sans-serif">More information is available at [1]. This depends on a gerrit plugin, but I believe it's enabled by default.</div><div dir="auto" style="font-family:sans-serif"><br></div><div dir="auto" style="font-family:sans-serif">[1] <a href="https://gerrit.googlesource.com/plugins/reviewnotes/+/master/src/main/resources/Documentation/refs-notes-review.md">https://gerrit.googlesource.com/plugins/reviewnotes/+/master/src/main/resources/Documentation/refs-notes-review.md</a></div></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="elided-text"><br>
</div></blockquote></div><br></div></div></div>