<p dir="ltr">Yep. Gerrit uses the ChangeId for recognizing logical equivalence, and assumes that the state of your repo at the time of your push to gerrit is how you would want the git history to look if the patches were then submitted immediately. So you can always push a chain of patches, and if gerrit recognizes any ChangeId, that change gets updated with new content and dependencies. I did this on the weekend for making 3952 depend on 4077.</p>
<p dir="ltr">Mark</p>
<div class="gmail_quote">On Sep 22, 2014 11:15 PM, "Szilárd Páll" <<a href="mailto:pall.szilard@gmail.com">pall.szilard@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
If you push Patch 2 based on Patch 1 and the latter is already in<br>
gerrit, the dependency should show up. You can even push a branch with<br>
multiple commits; theses will show up as a chain of dependent changes<br>
in gerrit.<br>
<br>
--<br>
Szilárd<br>
<br>
<br>
On Mon, Sep 22, 2014 at 11:10 PM, David van der Spoel<br>
<<a href="mailto:spoel@xray.bmc.uu.se">spoel@xray.bmc.uu.se</a>> wrote:<br>
> Hi,<br>
><br>
> I have two patches in gerrit that are both still under review. How do I<br>
> make, in hindsight, patch 2 depend on patch 1, such that I can use the code<br>
> from patch 1 in patch 2?<br>
><br>
> Thanks,<br>
> --<br>
> David van der Spoel, Ph.D., Professor of Biology<br>
> Dept. of Cell & Molec. Biol., Uppsala University.<br>
> Box 596, 75124 Uppsala, Sweden. Phone: <a href="tel:%2B46184714205" value="+46184714205">+46184714205</a>.<br>
> <a href="mailto:spoel@xray.bmc.uu.se">spoel@xray.bmc.uu.se</a> <a href="http://folding.bmc.uu.se" target="_blank">http://folding.bmc.uu.se</a><br>
> --<br>
> Gromacs Developers mailing list<br>
><br>
> * Please search the archive at<br>
> <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a> before<br>
> posting!<br>
><br>
> * Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br>
><br>
> * For (un)subscribe requests visit<br>
> <a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers" target="_blank">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a> or<br>
> send a mail to <a href="mailto:gmx-developers-request@gromacs.org">gmx-developers-request@gromacs.org</a>.<br>
--<br>
Gromacs Developers mailing list<br>
<br>
* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a> before posting!<br>
<br>
* Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br>
<br>
* For (un)subscribe requests visit<br>
<a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers" target="_blank">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a> or send a mail to <a href="mailto:gmx-developers-request@gromacs.org">gmx-developers-request@gromacs.org</a>.</blockquote></div>