'Re: clarification on git, central repositories and commit access lists' - MARC - 0 views
-
Another option is to look at git-svnserver which would allow a git repository backbone, but could talk svn over the wire which these tools could use...
'Re: clarification on git, central repositories and commit access lists' - MARC - 0 views
-
Btw, to see this in another light: as an example of a git tree that merges those same branches, but *before* they are ready, just look at the -mm tree. Now, Andrew actually ends up exposing the end result not as a git tree, but as patches, but what he actually *does* is to: - get my git tree - merge in about 30-40 other git trees from other developers (not all of which necessarily have actual development on them at any particular time) - then merge in his own patch list - expose it all as the -mm patch series So this is an example of how you actually have a totally separate, and still fairly central (the -mm tree is certainly now unknown outside of the core developer circles) tree, and where git is a big part in making a central "experimental" tree that is separate from my own central "development" tree. Also, it's an example of why centralization is bad: different people and entities have different intents. You could *not* reasonably do something like this with a centralized SCM like SVN.
Git Community Book - 0 views
Git - Fast Version Control System - 0 views
gittutorial(7) - 0 views
Welcome to GitCasts - 0 views
Git for the lazy - Spheriki - 0 views
Pro Git - Table of Contents - 0 views
git remove files which have been deleted | commandlinefu.com - 0 views
Understanding the Git Workflow - 0 views
Our Simple Git Workflow | Think Vitamin - 2 views
How GitHub Uses GitHub to Build GitHub - 0 views
Scott Chacon on the Interwebs - 0 views
How we use git at Shopify - Shopify - 1 views
« First
‹ Previous
61 - 80 of 87
Next ›
Showing 20▼ items per page