On Tue, 02 Aug 2016 10:44:49 +0100 Luis de Bethencourt <luisbg@xxxxxxxxxxxxxxx> wrote: > Looks like these patches are dropped from the -mm tree because they are already pulled > into linux-next via my git branch [0]. > > Forgive my inexperience with the process of adding git trees into the Linux development > process. When I asked Stephen to add the befs tree to linux-next I was thinking about > testing against any conflicts, but didn't realize about the impact from merging the > patches twice via -mm and befs tree. That's cool - this happens all the time. > I should've asked you the following before doing this: > How do you want to proceed with the befs file system patch flow? > > Aiming to make your life easier and taking some of the work load. I created the git tree > to make it easy to keep track of the patches Salah and myself Ack. I know these aren't > high priority in your list so wanted to make it easier. You can see there is a bunch of > patches in the for-next branch [1] where I have been the only reviewer and signed off. > > Then the question is about sending them to you in a tar ball/patch bundle/git pull, or > asking Linus to pull from my git tree. The latter means less work for you, which is part > of the goals, but needs to wait a little bit until I get my second and third signature in > my GPG key from kernel.org trusted people. If you prefer the former, let me know which > process you prefer, I know you aren't a fan of git pulls. Please ask Linus to pull the patches. > The timing isn't great, ideally we want these cleanup patches to go through in -rc1 and > after that the rest will wait for the next development cycle. Unless there is a bug fix, > which might happen since I am chasing some odd behaviour in befs_find_key(). > > Everything will go through the mailing list as usual and patches will sit on for-next at > least a week before moving to for-linus. That's OK. You might miss 4.8 but I don't think there's any rush on this material? -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
