Any interest in using git for scm?

[Blair Zajac]

On Nov 6, 2009, at 12:12 PM, Darren Weber wrote:

>
>
> On Fri, Nov 6, 2009 at 10:49 AM, William Siegrist  
> <wsiegrist at apple.com> wrote:
> On Nov 5, 2009, at 5:46 PM, Darren Weber wrote:
>
> >
> > After listening to Linus Torvalds talk about git and looking at a  
> video tutorial from Scott Chacon, it would seem beneficial to use  
> git for MacPorts development.  It appears that git can be used with  
> an existing svn repository (man git-svn), or the svn repository  
> could be imported into a new master git repository (perhaps host it  
> with github).  Is anyone currently using git for MacPorts development?
> >
>
> Mac OS Forge (the hosting provider MacPorts lives on) does not  
> currently provide read-write git repos. But we do provide a git  
> mirror of the svn repo.  That at least saves you some time when  
> creating your local git repo.
>
> https://www.macosforge.org/post/git-mirrors/
>
> -Bill
>
> In general, it is very interesting to see how git has evolved to  
> solve the challenges of distributed source code development for the  
> linux kernel.  It's able to handle thousands of files and hundreds  
> or thousands of contributors, with high performance and integrity  
> criteria.  While it's healthy to maintain some scepticism about  
> drinking any particular flavor of cool-aid, the git cool-aid looks  
> impressive ;-)  After listening to the Google tech talk from Linus,  
> one of the most striking things about git is the sha1 hash to  
> maintain integrity in the repo objects (other significant features  
> include the distributed repos for local work, true 'content'  
> management [full patches, not just file management], staging commits  
> like a transaction, easier and faster merging, etc.).  The sha1 is  
> used to guarantee that what goes in is exactly what comes out.  As  
> he put it, this evolved from an attempt to hack the linux source  
> code when it was managed under BitKeeper (which did provide a  
> detection for the hacks).  It's not exactly a security feature, it  
> provides an integrity check and a byproduct of that is the ability  
> to detect corruption.  The distributed nature of the git repos is  
> also a default backup system of a sort.
>
> Given the sha1 integrity checks in git (not available in any other  
> scm yet?), an import of source code from cvs, svn etc. into git is a  
> persuasive argument.  Are there any faults or gaps in that argument?

Don't drink too much of the cool aid :)

Subversion maintains a md5 hash of all committed items and does  
consistency checks upon them when there are any operations.  There are  
hashes in the repository and in the client side checkouts to ensure  
that all operations are done correctly.

Subversion 1.7 is going to be using sha1 hashes in some places where  
md5 hashes are currently used.

Blair