Week 13: Outreachy internship ends

INTERNSHIP ENDS Thirteen weeks have already passed since the beginning of the internship, and it seems like a blink. But re-reading my old entries and reviewing all work done, a lot of things have been achieved :). At the beginning, I was a very basic user of git commands, and now after one thousand rebases, cherry-picks, bisects, range-diffs,..I feel I have improved my git knowledge a lot. Many initial configurations or installations caused me a lot of struggling too but now it all seems much more easier. [Read More]

Week 9: Debugging

PATCH SERIES UPDATE This week, last patch series version (2) was sent, reviewed, and I have been implementing almost all suggestions in my latest branch. Comments and suggestions topics were about: commit message amending, one commit splitting and code minor fixes and improvements. Also, the issue about using an enum to represent bisect.c return code values, has arisen again. So this will be included in next version. After discussing with my mentor some doubts about remaining suggestions, I will send another version (third) to the mailing list and the cycle will start over. [Read More]

Week 8: First review received

PATCH SERIES FIRST ROUND REVIEW After sending the patch series to Git mailing list, I have received some useful reviews. First, one interesting recommendation was to split the series into smaller groups in order to be easily reviewed. Let me remind that patch series was composed of 29 patches. In this respect, I am preparing a new patch series version with 11 patches that corresponds to preparatory and clean-up commits and all bisect. [Read More]

Week 7: Patch series sent!

LATEST COMMITS With previous patch series very near to be sent, I started working on future patches. Previous patch series changes end with a complete conversion of all shell commands to C, but git-bisect.sh still exists. To finish the porting to C, we have to get rid of the shell file. My work now consists on implementing the remaining changes in step by step commits, checking that all things compile and tests pass. [Read More]

Week 2: Git rebasing and more!

Git rebase One of my tasks this second week was using interactive rebase to organize previous work. Interactive rebase, git rebase -i, is a useful and powerful command that allows you to change your commits in many ways such as editing, deleting, splitting and squashing. You must indicate how far back you want to rewrite commits by telling the command which commit to rebase onto. In my case: $git rebase -i HEAD~30 [Read More]