taapasX28's Blog

Final Checkin

taapasX28
Published: 08/25/2019

 

Hey everyone! This is my final blog post here. GSoC 19 has finally come to its end. This week I mostly worked on hg abort --update

What did I do this week?

This week I worked on writing intensive-tests for hg update --abort
As suggested by @mharbison72 I worked on cases where we need to take considerations of subrepos and check cases where a subrepo is dirty and cases where more than one subrepo is present and conflicts for one or more of them is resolved but not all conflicts are resolved so as to check the unmark feature. The patch is still under review but it too will soon get accepted.

Did you get stuck anywhere?
I did not get on anything major this week . I did have to perfect the code considering some endpoint cases but it came around fine enough.

 

Finally, I would like to  thank Pulkit for reviewing the patches and solving the doubts despite having a busy schedule, Martin and other people in the community for teaching the basic etiquettes and facts required to be a better open-source contributor and solving the doubts no matter how silly they were.

Adios !

View Blog Post

Coding Period: Week 10

taapasX28
Published: 08/04/2019

Hey everyone! This is what I did this week. In this phase, I worked mostly on the understanding of mergestate for developing a patch for hg update --abort. This is the last part that I need to complete before GSoC deadline.

What did I do this week?

As stated previously I worked on evolve and was able to get my patches for hg abort for evolve repository merged which included adding support for hg evolve and hg pick. Also, I worked on hg continue support and was able to add support for evolve. I will submit the patch for that once pick is also complete.
As for
hg update --abort I went through the code for hg resolve -u and
also
-at:local. I learned what merge state stores and started writing the code adding --abort flag for hg update.
I also received reviews for the continue patches I sent to the core repo and modified my patches according to that.

What is coming up next?

This week I am planning to complete support for hg continue for evolve. Also, I would send my first patch for hg update --abort.

Did you get stuck anywhere?

I got stuck with the logic of abort flag but @Pulkit pointed me to go through the code and documentation of mergestate which helped me get a better understanding of the workflow.

View Blog Post

Coding Period: Week 9

taapasX28
Published: 07/28/2019

Greetings everyone! Update for this week is as follows. In this phase, I sent the remaining patches required to complete hg continue support for core Mercurial repository.

What did I do this week?
As stated in the previous week I sent patches for hg continue for for graft, transplant and histedit. [1] [2] [3] [4]
I also created logic for hg transplant --abort[5] as asked by @Pulkit and added its support to hg abort plan [6]. These patches are still to be merged and under review.

What is coming up next?

This week I am planning to complete support for hg continue for evolve. Also, I will start my work on logic for hg update --abort which is one of the most demanded features for Mercurial.
My patches for
hg abort for evolve merged as they still left to get reviews as most of the people in the community are busy with the new version release.

Did you get stuck anywhere?

I did get stuck when I started with the logic for aborting a transplant but @Pulkit again helped me out of the situation and suggested that I should look into the recover method of the transplanter class.

View Blog Post

Coding Period: Week 8

taapasX28
Published: 07/21/2019

Hey everyone!  This is this update for this week. This blog describes basically how I started working on hg continue and got my first four patches approved.

What did I do this week?

This week I started my work on hg continue and sent the first patch regarding the logic for it [1]. Then subsequently I sent patches to add support for rebase[2] and unshelve[3] and also for graft and it was queued but as it wasn't too refined it had to be de-queued and sent the fix[4]. This leaves graft, tranplant and `histedit` to work on to complete hg continue plan.

What is coming up next?

This week I am planning to complete support for hg continue for graft, transplant and histedit and get that approved. Also, I will try to apply it move to evolve.
I also am still planning on getting my patches for
hg abort for evolve merged as they still left to get reviews as community is busy with the release.

Did you get stuck anywhere?

I did get stuck when I started adding support for the functions but @Pulkit again helped me out of the situation. I was not sure how to pass on the opts for various commands when continuefunc is directly called . But the knowledge that opts are present in state file resolved it.

View Blog Post

Coding Period: Week 7

taapasX28
Published: 07/14/2019

Greetings everyone!  This is this update for this week. This is all about how I
got
hg abort finally added to Mercurial. I also sent PRs to evolve repository adding its support.

What did I do this week?

This week I improved hg abort further and finally got them accepted and merged. This marks the end of hg abort plan for Mercurial core repository.
It will now be shipped with Mercurial version
5.1. It is still marked EXPERIMENTAL though as there is still a little doubt regarding its perfectness.
Also, my patch for bug code 6160 was finally merged. Completing integration with the core I moved to  Mercurial's
evolve repository and added support for hg abort for hg evolve --abort and hg pick --abort [1][2][3]. These patches are still under review.
I also started my work on
hg continue and was able to develop a logic for it and also apply it for histedit.

What is coming up next?

This week I am planning to start sending patches on hg continue on Phabricator. Also I will try to apply it for the remaining commands in core and then move to evolve.
I also plan on getting my patches for
hg abort for evolve merged.

Did you get stuck anywhere?

I did get stuck a little when working with evolve repository but @av6 and @marmoute covered most of them for me. Besides that I wasn't stuck in something that was major.

View Blog Post