Posts

Week 10 & 11

Hey folks, My internship is about to end in a week. I have learnt so many new technicalities. I loved my internship period. I will always remember this as a worth experience of my life. Talking about my project. I have successfully submitted my second patch series. Git mailing list link: https://public-inbox.org/git/ The changes that are introduced in the second  patch series are as follows: ## Changes since pranit’s v15 patch series #### bisect--helper: refer `branch.buf` before `strbuf_release(...)` #### bisect--helper: change `retval` to `res` #### bisect--helper: `decide_next()` helper function. #### bisect--helper: `bisect_next` and `bisect_auto_next` shell function in C ##### Divided this commit into nine commits 1. bisect.c: libify `exit_if_skipped_commits` to `error_if_skipped...` 2. bisect.c: libify `bisect_checkout` and its dependants 3. bisect.c: libify `check_merge_bases` and its dependents. 4. bisect.c: libify `check_good_are_ancestor

Week 8 & 9 - Project progress

Hi folks, I am very happy that my project "Improve git-bisect" is going well. I have learned so many git and C programming aspects that are great benefit altogether. Coming on to the progress of the project so far: I have completed the first internship task which is about finishing Pranit Bauva's GSoC work on converting `git bisect` from shell to C. And I am almost near to converting `git bisect` from shell to C completely. Pranit has converted many shell functions to C which were needed to be resolved, after the mentors and git mailing list reviewer's views. So, I resolved all the reviews that were present in the git mailing list and confirmed that all tests pass. These functions are as follows: ` bisect_reset() `,` bisect_write() `, ` check_and_set_terms() `, ` bisect_next_check() `, ` get_terms() `, ` bisect_terms() `, ` bisect_start() `, ` bisect_autostart() `, ` bisect_state() `, ` bisect-head() `, ` bisect_log() `, ` bisect_replay() `, ` bise

Week 6 & 7 - Modifying Expectations

Hi Folks, What was your original internship project timeline? Actually, I started the contribution to the Git project in late October and I didn't get much time to spend on the project timeline and therefore I was not able to submit the project timeline. I got my first mail to get started off with the project. My first goal was getting the last patch series of Pranit Bauva as commits in my git repo : [ https://github.com/tanushree27/git ] based on an old master branch and I had made sure that all the tests pass. Then based on an old master branch, I rebased it to a current version of master and then made sure that all tests pass again. After that, I had a look at what were the reviews/comments people made about the patch series and then tried to address those comments. What goals have you met? I have completed my first goal - Getting the last patch series of pranit bauva: So, firstly I started off by getting the last patch series of Pranit Bauva as commits

Week 4 & 5 - A week for the Audience

Hello everyone, I am very pleased to welcome you all to read my this week's blog which is just for you. Last two weeks were very busy for me and hope for you to as there was Christmas as well as New Year Celebrations back to back. I was quite busy with my internship work also. I'm glad to tell you that I have successfully submitted my first patch series in the Git Mailing List. You can find the link below. Link: https://public-inbox.org/git/pull.101.v17.git.gitgitgadget@gmail.com/#t It’s been a great experience working with the Git mailing List aspects and getting to know some interesting facts about it. Now, coming to the objective behind this blog. Basically, I will introduce you to my community and some concepts I have learned so far in this internship with my GIT Community . What kind of people participate in your community? Most of you must be aware of GIT (A stand-alone,open-source project and Github makes money by hosting git repositories). But for those who a

Week 3 - Progress and Struggles faced during the "Improve git-bisect"

Image
Hi folks, A slightly hectic but great week towards successfull completion of the project. I am getting the hang of Git now, various terms, features, and concepts are undoubtedly making sense now and the project is quite fruitful as an experience that enhances my ability to understand the things in a better way and build my skills in coding. This week tasks were: "--autosquash" my commits with pranit's old commit. Resolving the mentor's review issues after code pushed to Git. Creating separate patches for sending it to the git's mailing list. I have successfully completed my tasks for this week. Further, I am changing the description of the patch to the changes I had made so far and describing why I made those changes. Then the Patch will be ready to be submitted in the Git's mailing list for review. Talking about the struggles I faced so far in the project: ROADBLOCK: I would like to talk about the first roadblock that I faced in

Week 2 - Getting Started with the "Improve git-bisect" GIT project

Hi everyone, I am thoroughly enjoying my work with GIT. It is a wonderful experience with such mentors, who are always there to help me out, whenever I am stuck in the project. So, here is a brief about the work done this week. First of all, let me tell you that I have been working on “ Converting git-bisect.sh file to the bisect.c program ”. This project was undertaken earlier by a GSoC participant [Pranit Bauva], he was halfway through the project and now I am here to proceed with the project further. So, firstly I started off by getting the last patch series of Pranit Bauva as commits in my git repo : [ https://github.com/tanushree27/git ] based on an old master branch and I had made sure that all the tests pass. Then based on an old master branch, I rebased it to a current version of master and then made sure that all tests pass again.  After that, I had a look at what were the reviews/comments people made about the patch series and then tried to address those co