Changes between Version 2 and Version 3 of GitObjections

Show
Ignore:
Timestamp:
09/18/09 01:15:52 (5 years ago)
Author:
pmichaud
Comment:

refactor to make objections and answers a bit clearer

Legend:

Unmodified
Added
Removed
Modified
  • GitObjections

    v2 v3  
    11Objections to using Git as a VCS, per discussion at http://irclog.perlgeek.de/parrot/2009-09-17#i_1510436 . 
    22 
    3   * Integration with trac. http://trac-hacks.org/wiki/GitPlugin 
    4   * Demonstrate that git actually is better at resolving the merging conflicts we hit in real usage. - I know that specific examples would be great here, but does anyone actually doubt that merging is less painful in git? 
    5   * Source code browsing tools. (including revision browsing) gitweb? 
    6   * Down-time and retraining time for developers. 
    7   * Safety of the core source (limiting the damage possible accidentally or by new committers) 
    8     * (with git it's possible to make changes that destroy the history of the repository) 
    9     * Have a server side post-commit hook that disallows non-fast-forward updates. That negates any possibility of a newbie messing up the master Parrot git repo. Also, the history is not destroyed, just altered. The history is still there and could easily be fixed from another Parrot git repo. 
     31. Objection: Integration with trac.  
     4   * Answer 1.1: http://trac-hacks.org/wiki/GitPlugin 
     5 
     62. Objection: Demonstrate that git actually is better at resolving the merging conflicts we hit in real usage. 
     7   * Answer 2.1: I know that specific examples would be great here, but does anyone actually doubt that merging is less painful in git? 
     8 
     93. Objection: Source code browsing tools. (including revision browsing) 
     10   * Answer 3.1: gitweb? 
     11 
     124. Objection: Down-time and retraining time for developers. 
     13 
     145. Objection: Safety of the core source (limiting the damage possible accidentally or by new committers) 
     15   * Claim: (with git it's possible to make changes that destroy the history of the repository) 
     16   * Answer 5.1: Have a server side post-commit hook that disallows non-fast-forward updates. That negates any possibility of a newbie messing up the master Parrot git repo. 
     17   * Answer 5.2: Also, the history is not destroyed, just altered. The history is still there and can easily be fixed from another Parrot git repo.