Welcome to my second post in the series of lesser-known git commands. If you have missed last week’s post about git worktree you can find it here. This week we will look at git filter-branch. Hopefully, you will not need it that often but if you do git filter-branch is extremely powerful in rewriting your[…]
I thought I would start a blog post series about some lesser-known git features. So here we go! With no further ado let’s kick things off with git worktree. Normally if you clone a repository you are switching branches in your working directory. But let’s imagine you don’t want to or are not able to[…]
Last weekend I visited the FrOSCon 14 in Sankt Augustin. The FrOSCon is a two day conference that’s completely free for visitors and focuses, as the name indicates, on free and open source software. On Sunday a gave a talk about git “Git Fu Developing”. You can watch the recording either on the CCC website[…]
Most parts of the libraries I maintain are written by me. So why is it, that I try to write good comments and good commit messages, even if I might be the only one ever reading them again.
A while ago I had a look at our git commit messages and found myself in some kind of a whatthecommit mess. I remember clearly that we agreed on doing commit messages the git, or as I call it, the Beams way, don’t worry, I’ll explain what that means a bit later. But agreeing obviously wasn’t enough, to actually follow the rules.
A while ago I gave a short talk at our office in Frankfurt. I talked about 10 git tips that come in handy when doing version control with git.