Hello Everyone, I'm new to the list so I figured I'd introduce myself instead of just wall-flowering... "Hello"... :) Anyway, I really like a lot of the concepts found in Git and the reported power and flexibility of it are very intriguing. However, there are some issues that I can't wrap my head around, such as how you can guarantee that all developers are working on the same code-base without a central repo. I would classify a lot of my issues as paradigm rather than technically related. I understand a lot of Git's underpinnings and the basic usage of it, I just can't wrap my head around the higher-order parts of it. I've done some Googling and I can't find a good 'Introduction to Distributed SCM Concepts for Centralized SCM Developers' article yet. Ideally, this would be an article all about the high-level thought processes that go into utilizing Distributed SCM in a team environment where having a single canonical representation of your project that all developers are working off of is important. Anyway, looking forward to participating. P.S. Anyone want to tell me why the Git Mailing List was set-up monolithically rather than the typical git-dev, git-user, git-admin, git-x etc.? I don't plan on hacking on Git so having the Dev mail in the list is just noise for me. I'm sure other people think that too. Just wondering. -- In Christ, Timmy V. http://burningones.com/ http://five.sentenc.es/ - Spend less time on e-mail -- 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
