My Ride
Started: Friday 24th May 2013 4:33pm
Distance: 17.46km
Duration: 00:39:15
Rest Time: 00:06:05
Climb: 124m
Max Speed: 51.48kmph
Average Speed: 26.68kmphInstagrams
-
Recent Posts
Recent Comments
- Arie on Tag Time: CakePHP Tag Plugin
- Paul on Sign Me Up A CakePHP User Registration Plugin
- Paul on Sign Me Up A CakePHP User Registration Plugin
- Watch The Big Bang Theory season 6 episode 13 on On My Tv: With Trakt.tv
- veloura et bellagenix on Ultimate Guestbook Tutorial: How to build a Guestbook with a honeypot, error checking, IP banning, pagination, e-mail notification and smilies with PHP and mySQL
Archives
- February 2013
- December 2012
- September 2012
- July 2012
- January 2012
- September 2011
- August 2011
- February 2011
- January 2011
- November 2010
- October 2010
- August 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
Categories
Meta
When to Branch
August 20, 2009,
299 views
So i’m learning about source code version control, with Git. This explains the art of when to create a branch. More so for my furture reference:
- Experimental changes: Want to try rewriting algorithms just to see whether they’re faster, or want to try refactoring a section of code to a particular pattern? Create a new branch to do your work in, and you can work on it separately from any changes that are being deployed immediately.
- New features: Every time you start working on a new feature, create a new branch. You can merge it back in as soon as you’re done, either with the full history or through a squashed commit.
- Bug fixes: Whether it’s a fix to a bug in code that hasn’t been released or code that has already been tagged for a release, you can create a branch to track your changes to that bug. This gives you a lot of flexibility in how you merge it back into the rest of the code, just like creating a branch for a new feature. This is especially true if your bug fix is going to take some experimentation.
Categorised under Software





