I am working with git and I'm wondering if coding like the following is a good way to manage code: create code then commit when a good set up code is ready push to master create a branch create code then commit when code is good, merge and push to master go back to create branch Anyone else have a procedure they go through when managing code? thx, -wes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html