Re^2: Periodic Save As

I've got to agree here, although when you are the sole developer you don't usually need to worry about things like branches. I even keep my agenda and similar files in a revision control system, and I have gone back to view old appointments. As an added bonus, it's a nice way to keep everything synced between the different desktops I use and the server with the repository gives off-site backup without me having to think about it.

I can't imagine not wanting to use revision control for code, especially when it takes so little effort to use a minimal subset of features properly.

Comment on Re^2: Periodic Save As

Replies are listed 'Best First'.
Re^3: Periodic Save As by gregor42 (Parson) on May 23, 2008 at 13:35 UTC
Branching is simply a necessary evil when distributing releases to a user-base. This is because you will want to work on the next major release while still being able to produce patches for past releases. It is likely that you will want to merge your patch into the next release at some point, but that is a subsequent task to developing the patch in the first place. Wait! This isn't a Parachute, this is a Backpack!	[reply]
Re^4: Periodic Save As by kudra (Vicar) on May 23, 2008 at 16:54 UTC
That's true. I was thinking in terms of single-writer single-user projects (like my agenda!)	[reply]