An interesting idea on tracking pain points in a project with git history.
 
#git #legacy #tool

An interesting post in Git mailing list: creator of JGit describes, what they have to do in order to make their Java implementation of Git faster and why they are still slower than C implementation.

#git #c #java

In the beginning was the Word, and the Word was Pain. Because how else would you call the process of manually merging multiple Linux Kernel patches? BitKeeper was after. Didn't make it. Then Git was built. And here we are.
You'll find the story of Git origins in this post. What VCS existed back then, what was wrong with them, what did Linus want, why did he pause Kernel development at some point and build a tool that is used by the majority of developers today.

#git #history

We've been using this approach for a long time, but it turns out, there's a smart-ass name for it: Stacked PRs. In short: instead of submitting one fat pull request with your feature, you submit several small dependent PRs. It works well with github, however there are still some things to be done manually. Author highlights, which parts we'd probably like to perform automatically or in an easy way, and which tools could potentially help us with that.

#git #tool

Check out this mind blowing tool! It visualizes project history using repo data. Repo is here.

#tool #git