Comments on: Version Control Habits of Effective Developers http://blog.bstpierre.org/version-control-habits Software Development, version 3.0 Fri, 05 Mar 2010 15:01:53 -0700 http://wordpress.org/?v=2.8.5 hourly 1 By: Dieter http://blog.bstpierre.org/version-control-habits/comment-page-1#comment-2704 Dieter Tue, 26 May 2009 15:20:21 +0000 http://blog.bstpierre.org/?p=61#comment-2704 Excellent article! I'd like to switch to Git to use private branches, but unfortunatly I can't miss the SVN integration in Eclipse, and TortoiseSVN is also mighty handy. I'm currently implementing Hudson CI, the holding branch is a good idea! Probably going to implement that. I'm going to print your article and hang it on our messageboard somewhere :) . Excellent article!

I’d like to switch to Git to use private branches, but unfortunatly I can’t miss the SVN integration in Eclipse, and TortoiseSVN is also mighty handy.

I’m currently implementing Hudson CI, the holding branch is a good idea! Probably going to implement that.

I’m going to print your article and hang it on our messageboard somewhere :) .

]]> By: Jakub Narębski http://blog.bstpierre.org/version-control-habits/comment-page-1#comment-22 Jakub Narębski Fri, 09 Jan 2009 12:32:34 +0000 http://blog.bstpierre.org/?p=61#comment-22 <b>Write good checkin comments</b>: I think Git commit message convention is a good idea to follow here: single-line "subject" of changes, short description of a commit, separated by empty line from more detailed description of changes. Also for open-source projects it could make sense to apply Linux kernel and git project signoff (certificate of origin) policy. Write good checkin comments:

I think Git commit message convention is a good idea to follow here: single-line “subject” of changes, short description of a commit, separated by empty line from more detailed description of changes. Also for open-source projects it could make sense to apply Linux kernel and git project signoff (certificate of origin) policy.

]]>