So, after a long while, I wrote a new C language program. As usual, the same things that I dislike about C programming popped up, specifically the need for low level data structures and manual memory management. I did learn some new things: ...
Testing, code coverage, style enforcement are all check-in and merge requirements that can be automated and driven from Git. If you're among the rising number of Git users out there, you're in luck: You can automate pieces of your development workflow with Git hooks. Hooks are a native Git mechanism for firing off custom scripts before or after certain operations such as commit, merge, applypatch, ...
This is an article about different media (and more specifically) video files can be manipulated. This is just for historical purposes as now almost everything can be done using ffmpeg and the right options. libmp4v2 contains: ...
So these are my ideas on how to document projects. There are three types of documentation types: User guides Targetted and end-users of the software and people who want a brief overview. Man pages Again targetted at end-users but also sysadmins. Usually to address a specific feature. ...
Sharing repositories Rewriting history Rolling back the last commit ...
Use DVCS as backend (GIT) Output html markdown Prefer perl/python Mostly RO so to avoid merge conflicts. ...
Start working on a Topic Branch Keep Topic Branch current Merge a Topic Branch Start working on a HotFix Keep HotFix Branch current ...