couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Update of "SVNvsGIT" by MarkStruberg
Date Sat, 19 Nov 2011 09:21:57 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "SVNvsGIT" page has been changed by MarkStruberg:
http://wiki.apache.org/couchdb/SVNvsGIT?action=diff&rev1=2&rev2=3

  == Main difference between SVN and GIT ==
  For understanding the setup of our GIT repositories better, we have to understand the difference
in the mechanics of GIT compared to what we had available before at the ASF.
+ 
+ This matrix should also help to understand when a project might choose GIT or better shall
stick to SVN. As an example: If you have a heavily modularized project where each module has
it's own lifecycle, then better stick with SVN. In GIT this scenario would require to create
an own GIT repository for each and every submodule, which would make releasing them as a bundle
a real nightmare!
+ 
  ||<tablewidth="903px" tableheight="203px"> ||SVN ||GIT ||
  ||Content ||SVN handles the content on a per-file basis. Each file is basically versioned
on it's own and has it's own history. Moving a file with svn mv will preserve this history.
Just copying the file will not! ||GIT treats all the files in the repository as a big union.
All the commits basically form a tree of diffs which get applied to the initially empty project
directory. There is no 'native history' on a file basis because of that. For producing a git-log
or git-blame, GIT needs to walk through all the commit tree and check whether the given file
is involved. Otoh git can not only automatically track rename-files, but also perfectly tracks
if you move a method from one class to another! ||
  ||Security ||Handled by SVN itself. It's perfectly possible to have different directories
and files in a SVN repo which have different security rules applied. ||GIT has no own security.
It solely relies on the underlying transport/filesystem. It's not possible to have a 'hidden'
branch which is only readable by certain people. Otoh one can create pre-commit hooks to only
allow certain people to push to some specified branches.y ||

Mime
View raw message