On 7 Sep 2017 6:25 pm, "Niels de Vos" <ndevos@xxxxxxxxxx> wrote:
On Thu, Sep 07, 2017 at 04:41:54PM +0530, Nigel Babu wrote:That answers my question, I don't need to try it out myself.
> 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.
Thanks!
Niels
_______________________________________________
maintainers mailing list
maintainers@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/maintainers
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.
More information is available at [1]. This depends on a gerrit plugin, but I believe it's enabled by default.
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
