Hi Junio, On Wed, 22 Aug 2018, Junio C Hamano wrote: > Junio C Hamano <gitster@xxxxxxxxx> writes: > > > Here are the topics that have been cooking. Commits prefixed with > > '-' are only in 'pu' (proposed updates) while commits prefixed with > > '+' are in 'next'. The ones marked with '.' do not appear in any of > > the integration branches, but I am still holding onto them. > > Mentors (and GSoC students), > > Two topics your students have worked on conflict heavily at the > philosophical level; "rebase in C" rewrite assumes that backend > implementations are forever written in shell and can be invoked by > dot-sourcing ". git-rebase--$backend", while violating that > assumption is the whole point of "rebase-i in C" rewrite. Trying to > use them together would of course not work without a bit of "last > mile" further glue. > > I do not think neither topic is ready for the upcoming release, but > can you help your students to come up with "the final step" to make > the fruits of their effort work well together? Pratik is unfortunately unable to spare time, as the university schedule in Nepal does not really have such a thing as summer break. He made a heroic effort to work on GSoC nevertheless, and I am quite proud of how much he learned, and that he managed to finish the patches (with my help). As I have a vested interest in a substantially faster `git rebase` on Windows, I will take care of the `rebase-in-c*` patches. FWIW I am a lot more bold about these builtins, and want to get them into Git for Windows v2.19.0, either as full replacements, or like I did with the difftool: by offering them as experimental options in the installer. Maybe this will remain a dream, but maybe, just maybe, I will manage to do this, with your help. Ciao, Dscho
