U TURN in the project and worked on further improvements required in the previous patch series.

Progress:

Last week received some more suggestions on the v4-patch series, which includes removing a bug - need to fix datatype of flag argument as it was used as combination of bits but was declared as enum todo_flag_items. Next it includes some fixes in the commit messages, updating the test script t3437 and lib-rebase.sh and some other minor fixes (Thanks to Eric Sunshine for the detailed reviews). After discussing with the mentors and on the mailing list, I updated the patches and sent a v5-patch series. Oops, that was a mistake!

Here I will mention to keep track of the patches in “What’s cooking” frequently sent by Junio to the mailing list.

Now as the v4-patch series was already merged to next branch so v5 revision was of no use as changes were done with interactive rebase and instead it is required to be done incrementally on the top of merged branch Instructions.

Command to find the tip of what got merged in “next” :

“git log --first-parent --oneline master..next”

(Thanks to Junio for guiding in detail as here)

So, this time sent a new patch series Patches-Improve the fixup [-C -c] in interactive rebase built incrementally that includes the changes of v4-patches and also some additional changes in the test script suggested by Phillip. Also received some more reviews on that and worked on updating those, below is the link of the latest patch series sent on the mailing list :

Patches: V3-Patches-Improve the ‘fixup [-C -c]’ in interactive rebase

Also, while working on the reviews I got stuck and wondered How to make different commits for different changes in the same file ? After discussing with mentors I got way out and learned about the git add -p, git patch mode which is a really very powerful command. Besides this another common issue is How to undo a git rebase ? Hint: use git reflog and git reset Read More.. Also, I learned that git reflog branch_name usually eases out the things in comparison to the git reflog which outputs the HEAD reflog.

TODO:

Will continue to work on some more improvements in the next patch series (to be sent on the mailing list) of implementation of amend! commit and here is the latest work-branch of it.

Thanks for reading !