Hello Jean-Marc, > Is it still the case with my latest patch?
I checked and it seems not. So, I think I have to remove my temporal patch and rearrange the code according to your suggested patch in the other message. I will try testing with that. > We also have to think about how to prepare this code to put it in a > repository for google review. The code should go to gsoc/scroll/master > in coherent commits that implement functionality bit-by-bit. The commits > should have a nice log that is explanatory. The hard date for having > this ready is Sept 23 (next Monday). It is reasonable to limit ourself > to this keyboard scrolling part, but it should work well in most cases. Will we be able to show the same repository under, gsoc/scroll/master? Or I can create a repository in my GitHub account. As the in between codes are not that stable, I have not push to the master frequently. I am not that familiar with pushing previous commits to the master from another branch (testing). What I know is, git push <remotename> <commit SHA>:<remotebranchname> And that will move all the commits upto the defined commit. Cannot we submit a wiki containing commit links with proper logs? I also see that there is no time to complete the UI based solution. But I would like to work with your help after the final submission. Thank you Hashini
