<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Aug 29, 2016 at 10:55 AM, Poornima Gurusiddaiah <span dir="ltr"><<a target="_blank" href="mailto:pgurusid@redhat.com">pgurusid@redhat.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Hi,<br>
<br>
Regarding the enforcement of the dependencies while merging, i see that<br>
the dependent patches on any patch is mentioned in the "Related Changes"<br>
column [1]. It still doesn't enforce, in the cherry-pick way of<br>
submitting changes, by default it ignores the lineage [2]. But there are<br>
ways to enforce this. Will let the gluster infra maintainers to comment<br>
on the same.<br>
<br>
[1] <a target="_blank" rel="noreferrer" href="https://gerrit-review.googlesource.com/Documentation/user-review-ui.html#related-changes">https://gerrit-review.<wbr>googlesource.com/<wbr>Documentation/user-review-ui.<wbr>html#related-changes</a><br>
[2] <a target="_blank" rel="noreferrer" href="https://gerrit-review.googlesource.com/Documentation/project-configuration.html#project_options">https://gerrit-review.<wbr>googlesource.com/<wbr>Documentation/project-<wbr>configuration.html#project_<wbr>options</a><br>
<br>
Regards,<br>
Poornima<br></blockquote><div><br></div><div>Thank you Poornima for pointing this out. You're right, it's worth changing our submission type to either "Rebase If Necessary" or "Merge If Necessary" to enforce this. I'm not sure what the implications are, so I'll report back after I've setup a test on staging so we can experiment and see what works.<br clear="all"></div></div><br>-- <br><div class="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</div></div>