On Sun, Jun 11, 2017 at 3:57 PM, Dibyendu Majumdar <mobile@xxxxxxxxxxxxxxx> wrote: > Hi Luc, > > On 11 June 2017 at 23:46, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: >> On Sun, Jun 11, 2017 at 11:02:40PM +0100, Dibyendu Majumdar wrote: >>> I was wondering if the sparse-next branch is going to be stable soon. >> >> As far as I know, sparse-next is very stable. >> Are you aware of any instability? >> > > I don't actively use sparse-next so I don't know of any. Good to know > that sparse-next is stable. I want to clarify that, "stable" you mean the code quality is good (no obvious bugs or crashes), or the git branch will not be roll back. As for the code quality, I believe that is reasonable stable. As for change roll back, the sparse-next is created with the goal to test out some of the newly merge changes. In theory rolling back history is possible with sparse-next if we find out some thing seriously wrong with the purposed changes. So it is not a stable point if you want to base your change on. The master branch will not roll back history, that is a more stable branch. >> But yes, all the LLVM patches I suppose you're interested in >> haven't yet made it and sparse-next itself still need to be >> promoted to master. >> > > I am interested in merging all the other changes too - but I wanted to > do this when all of the outstanding changes are included. > > Is there a specific goal for the next release of sparse, or will it be > just a point in time snapshot of sparse-next? Yes, I will do a very brief release of sparse just to flush out the new change into a version. Then we are going back to merge Luc's other changes. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
