On Thu, Aug 10, 2017 at 6:58 AM, Dibyendu Majumdar <mobile@xxxxxxxxxxxxxxx> wrote: > Hi, > > I would like to propose moving Sparse development to github. The model > I would like to propose is as follows: It does not need to be move from the release stand point of view. I already have an github account and github repository of sparse. I can merge the merge request from github (not using the github UI though). The merge will reflect on github. That should satisfy most of your points here. A lot of time is spend on the discussion and figure out what is the right thing to do. I still like the review before commit model. If Luc want to make this is clear this is a git pull request I want this pull. It be pull rather quickly using the current master model. A lot of time I need to clarify weather the patch is for release or for view. I can sync the master to github every time I push to korg. That part is easy. I am not a big fan of using the github UI for merge though. I can read the github issue request there fine. What you are really asking is having Luc on github has his own sparse tree. Not just patches. I totally support of that too. I would be happy to pull from his tree. I still prefer the review and merge model for release though. Thanks 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
