On Tue, Aug 24, 2010 at 09:31:21AM -0600, Wes James wrote: > 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 >From what you say, it sounds like you are using topic branches, which are always a good way to manage code. You might want to consider using release branches (like how git.git has "master", "next", and "maint"). I'm not sure what you mean by "push to master". You don't push to a branch. You push to a repository. I guess you mean pushing to the "official" or "blessed" repository? Also, sending patches to an email before merging to master is a good idea to get code review. -- 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