Hello, We're looking at Git at our company, and in the first phase of testing Git passed the technical criteria with flying colors, and did much better than Hg. We've entered the second phase of testing where I need to basically try out the typical work flows in Git. We have multiple teams, lots of developers, and would like to use a variant of the dictator-lieutenant scheme discussed in published subject matter. However, I find it rather challenging finding any subject matter that provides reasonable detail. What I'd like to find are concrete examples, step-by-step, of specifically how to: * set up each public repository: mainline, integration, maintainers, feature - with enough detail showing how to set up remotes, branches for each, shared or not, ... * perform the daily function for role, dictator, lieutenant, maintainer - with specific detail about the typical commands used each day Surely someone must have documented this somewhere, or perhaps scripted it up in some shell scripts which would be even better? I have spent multiple days on this already, and given that I am a novice at Git, though not with source control systems, if I could obtain some concrete examples, this would accelerate the evaluation quite a bit, and it would help me decipher the mounds of documentation with the few more concrete examples. I'd like to present the details and results to our development organization next week, and be able to speak about some flows I actually tried out myself. By the way, Git, love it! Way cool guys. A puzzled newbie, Bob -- 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