cloning a repository from somewhere else, isn't even covered until Chapter 12, because understanding what cloning really means requires so much background
That's... that's... just... what?
Cloning is part of the brutally simple (and amazingly flexible) guts of git. Given Linus's hatred of C++ I think what git has become is deliciously ironic, but the basics could not be easier to understand.
Do you know if it has any sort of mechanism for holding submits until approved? We're currently using Subversion and the general consensus on that one is giving everyone their own dev branch, then having the overseer handle merging, which is tolerable for some small number of developers.
You can also do it the same way you do with subversion though in which everyone has commit/push access to the same repo and just create a lot of branches.
And obviously you can mix the two methods just fine.
The Github model works great in Enterprise situations that typically have a single, shared repository. The key is that you actually need the Github software. Git is an unfinished product and Github finishes it. The answer to GP's question is to either host code at Github or install their Enterprise [github.com] software.
Cloning is portrayed as complicated?? (Score:3)
cloning a repository from somewhere else, isn't even covered until Chapter 12, because understanding what cloning really means requires so much background
That's ... that's ... just ... what?
Cloning is part of the brutally simple (and amazingly flexible) guts of git. Given Linus's hatred of C++ I think what git has become is deliciously ironic, but the basics could not be easier to understand.
Re: (Score:2)
OT, but since you seem to be familiar with git:
Do you know if it has any sort of mechanism for holding submits until approved? We're currently using Subversion and the general consensus on that one is giving everyone their own dev branch, then having the overseer handle merging, which is tolerable for some small number of developers.
Re:Cloning is portrayed as complicated?? (Score:2)
https://help.github.com/articles/using-pull-requests [github.com] works well when you let everyone have their own "fork" but afaik wouldn't work for a single shared repository.
You can also do it the same way you do with subversion though in which everyone has commit/push access to the same repo and just create a lot of branches.
And obviously you can mix the two methods just fine.
Re: (Score:0)
The Github model works great in Enterprise situations that typically have a single, shared repository. The key is that you actually need the Github software. Git is an unfinished product and Github finishes it. The answer to GP's question is to either host code at Github or install their Enterprise [github.com] software.