On Tue, 1 Dec 2015, Or Gerlitz wrote: > We're against into this... upstream is on 4.4-rc3 while your latest branch in > kernel.org (the one that carries thefor-next tag) is rebased to 4.3-rc3... Seems that everything was merged? So you can directly use 4.4-rc1 until he comes up with a for-next for 4.5. > --> our internal build and review systems for patches to linux-rdma can'tmake > any use of your tree. People here have to rebase their work against their own > clones of Linus tree and can't work with our internal Gerrit rdma-next branch, > etc, etc. AFACIT The primary use for the next-trees is testing and merging. You should be basing your work on 4.4-rc1 and all the patches you are carrying need to apply to 4.4-rc1 cleanly. Unless you depend on functionality that was added for the next merge cycle of course. But since there is no tree yet nothing was added so there is nothing there for you to rely on. Please do not base patches by default on -next tree's unless there is a good reason for it. If you do otherwise the code base will change too frequently. If the maintainer decides to drop a certain patchset your patches may no longer apply cleanly. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
