Currently I have about 30 tabs open in the browser on my phone. Quite a bunch of them I have open because I want to read the article in the future, already have read the article and want to reread or act on it, or a combination of the above. In this article I list the open tabs (and some notes) so I can close them on my phone, but still have a reference to them.
When I started on a project it seemed to make sense to put a part of the project in a separate Git repository. In hindsight that wasn’t such a smart move. Here’s how I fixed it.
On 19 February I held a presentation for my colleagues about distributed version control systems (DVCS). My main goal was to inform them on what I think is the next logical step in source control.
This blog entry is about a real life example of how the flexibility of Git made my life easier. It’s a story about how I stopped developing a feature halfway to try out an alternative, without throwing away anything or cluttering up the (Subversion) repository.
While I’m enthusiastic about Git, I still have to communicate with Subversion repositories like the Plone Collective. I also like my editor (Emacs) to help me interact with Git. In this blog entry I’ll explain how I setup my work environment.
After using Subversion for a couple of years, it’s time for me to look to the next generation of source control management systems.