Re: Hello All and Seeking Information
"Tim Visher" <tim.visher@gmail.com> writes:
Show 13 quoted lines
> 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.
The idea behind Git repository format is content adressed filesystem, which if I remember correctly was taken from Monotone (well, not addressed by actual content, but SHA-1 cryptographic hash of content+type). So if there is 134b8687c59e65ce06562ffb0e8be63ab7aa618b object in some repository, it is the same object in all repositories, even if it was created independently. That is one thing.
The other thing is that typical workflow calls for downloading changes (fetching in git jargon) from some 'upstream' repository, the official repository (one of official repositories) with code you are supposed to base your changes upon.
Also easy to create branches, and very good support for merging (and rebasing) makes it possible and easy to join (merge) lines of development done independently from some older point of history. So that even if you are not working on the same code-base I can incorporate your changes, and you can incorporate mine.
Show 7 quoted lines
>
> 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.
See http://git.or.cz/gitwiki/GitDocumentation (and also main page of this git wiki, Documentation mentioned on git homepage (http://git.or.cz) including "Git User's Manual", and "The Git Community Book" at http://book.git-scm.com
Show 5 quoted lines
> 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.
Because this Git is not so large project, and traffic on git mailing list is not so large to support split? IIRC there was "Git for Human Beings" aka git-users Google Group, but it doesn't seem to be there any more. Also having common mailing list allow for better contact between developers and git users (which hopefully would allow us to avoid comon pitfalls with 'developers for developers' approach).
--
Jakub Narebski
Poland
ShadeHawk on #git
Tim Visher
