[Gluster-devel] Changing Submit Type on review.gluster.org
Niels de Vos
ndevos at redhat.com
Thu Sep 7 12:55:42 UTC 2017
On Thu, Sep 07, 2017 at 04:41:54PM +0530, Nigel Babu wrote:
> On Thu, Sep 07, 2017 at 12:43:28PM +0200, Niels de Vos wrote:
> >
> > Q: Can patches of a series be merged before all patches in the series
> > have a +2? Initial changes that prepare things, or add new (unused) core
> > functionalities should be mergable so that follow-up patches can be
> > posted against the HEAD of the branch.
> >
> > A: Nigel?
> >
>
> If you have patches that are dependent like this:
>
> A -> B -> C -> D
>
> where A is the first patch and B is based on top of A and so forth.
>
> Merging A is not dependent on B. It can be merged any time you have Code Review
> and Regression votes.
>
> However, you cannot merge B until A is ready or merged. If A is unmerged, but
> is ready to merge, when you merge B, Gerrit will merge them in order, i.e.
> first merge A, and B automatically.
>
> Does this answer your question? If it helps, I can arrange for staging to be
> online so moe people can test this out.
That answers my question, I don't need to try it out myself.
Thanks!
Niels
More information about the Gluster-devel
mailing list