Or why a clean commit history can help quite a lot to find how and why a bug was introduced. This shows a few nice tricks around git log to speed up the process.

Looks like an interesting Git user interface. I'll take it out for a spin.

Good explanations on how HEAD works in git and what it means. It's indeed one of those terms where the consistency isn't great in git.

Looks like an interesting approach for a new family of development forges. Fully distributed and peer to peer, I wonder if it'll pick up.

Good reminder that git worktrees exist. They definitely come in handy sometimes.

Going back on the history of the introduction of version control in software engineering and how Git ended up so dominant. We often forget there was a time before Git.

Nice list of tips and recent git features to manage large repositories.

Looks like a nice way to automate the creation of changelogs.

Plenty of good tips in there. I knew quite a few, but there are a few nuggets that I'll test drive I think.

Can definitely recommend. The pre-commit project also make managing those a breeze.

So, which team are you on when you think about commits in Git?

It looks like git workflows using rebase are becoming the norm. People are actively trying to avoid merge commits in their repository history. Tooling support could be a bit better though.

Back to the history of VCS, anyone still remember and used SCCS? Well, I did use it...

Interesting statistics, this show how important it is to have well structured and focused change sets as much as possible.

Ever wondered how git implements cherry-pick and revert? Here are a good way to understand them. Also explains what is the 3-way merge git uses widely.

I tend to encourage people to master git rebase. In any case this comes with a few warnings so do it with care. This article does a good job pointing the caveats of the rebase command.

You still find git confusing? This article might help. Although I have doubts that it's doing a good job regarding heads, HEAD and branches, the rest is full of good explanations.

This is pretty much exactly how I organize my projects. I highly recommend this approach, works very well.

A good reference on most of the branching patterns you can find. From this you can derive your project wide policy. Also it's spot on when it says that branching is easy but each time you branch you need to keep in mind how you're going to merge.

Looks like an interesting alternative to Git. To investigate I think.