Diff for /wikisrc/gitsofar.mdwn between versions 1.4 and 1.10

version 1.4, 2015/02/16 01:44:18 version 1.10, 2019/09/03 01:16:05
Line 1 Line 1
 ## NetBSD with git so far  ## NetBSD with git so far
   
 [core statement on vcs](http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html)  * [[mailing-lists/tech-repository]]
   * [[projects/project/cvs-migration]]
   * [[github]]
   * [2011-10: Fossilizing NetBSD: The road to modern version control](https://2011.eurobsdcon.org/papers/sonnenberger/fossilizing.pdf)
   * [2015-01: Core statement on version control systems](http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html)
   * [2017-06: New home for the repository conversion](http://mail-index.netbsd.org/tech-repository/2017/06/10/msg000637.html)
   * [2017-09: pkgsrc Commit Message Policy](http://mail-index.netbsd.org/pkgsrc-users/2017/09/12/msg025574.html)
   * [GitHub.com/NetBSD](https://github.com/NetBSD)
   
 ### Low memory hosts:  ### Low memory hosts:
   
Line 22  git is slow during 'status' by default s Line 29  git is slow during 'status' by default s
 change.  It will produce a warning with tunable options if the command runs  change.  It will produce a warning with tunable options if the command runs
 slowly.  slowly.
   
 ** Update  *Update*
   
 After some complaining on the git@ mailing list a patch has been produced which  After some complaining on the git@ mailing list a patch has been produced which
 drops the memory requirements down quite a bit.  I can now, without much tuning,  drops the memory requirements down quite a bit.  I can now, without much tuning,
 work on my 512 system.  I'm pretty sure a 256 + swap without any special tuning  work on my 512 system.
 would also work.  
   
 ### CVS in parallel  ### CVS in parallel
   
Line 43  See above for CVS server provided if ong Line 50  See above for CVS server provided if ong
   
 ### existing cvs dependencies  ### existing cvs dependencies
   
 TBD  is there a list of these?  build systems?
   The entire build infrastructure of NetBSD should (even without giti) change into a "jobs"-oriented workflow instead of a "server"-oriented workflow.
   
   Very recent (summer 2017) events have shown that the ability to move things around is very important.
   
   
 ### How should NetBSD be setup  ### How should NetBSD be setup
   
Line 55  Also see a great description of how Drag Line 66  Also see a great description of how Drag
 [dfbsd workflows](http://lists.dragonflybsd.org/pipermail/users/2015-January/207422.html)<br>  [dfbsd workflows](http://lists.dragonflybsd.org/pipermail/users/2015-January/207422.html)<br>
 [dfbsd config](http://lists.dragonflybsd.org/pipermail/users/2015-January/207424.html)<br>  [dfbsd config](http://lists.dragonflybsd.org/pipermail/users/2015-January/207424.html)<br>
   
   [In 2019, FreeBSD core team has appointed a WG to explore transition from Subversion to Git.](https://www.freebsd.org/news/status/report-2019-04-2019-06.html#FreeBSD-Core-Team)
   
 ### how to install  ### how to install
   
 git should fit into NetBSD src/tools easily.  I have not personally tested  git should fit into NetBSD src/tools easily.  I have not personally tested
Line 85  Also using the dates for commits instead Line 98  Also using the dates for commits instead
   
 ### how to convert  ### how to convert
   
 ESR?  https://github.com/netbsd/
   
 ### No lock-in  ### No lock-in
   
Line 95  Don't do anything weird like change hist Line 108  Don't do anything weird like change hist
 Maybe when we have 30 years of project history it will be time to consider  Maybe when we have 30 years of project history it will be time to consider
 restructuring the project.  :)  restructuring the project.  :)
   
   git is the most widely used VCS ever so it has the best chance of conversion tools existing.
   No future tool will be able to exist without a git-conversion script.
   
 ---  ---
   
 I think this is less a function of the tool and more a function of the project not  I think this is less a function of the tool and more a function of the project not
Line 102  allowing non-"standard" actions. Line 118  allowing non-"standard" actions.
   
 ### Who, When, and How Long?  ### Who, When, and How Long?
   
 * ESR/Joerg - convert  * ESR/IIJ/Joerg - convert
 * sometime, eventually, maybe  * sometime, eventually, maybe
 * assumptions/proposal:  * assumptions/proposal:
   
Line 110  Assuming conversion starting from date(x Line 126  Assuming conversion starting from date(x
 refinements of Joerg/ESR conversion can continue to run in read-only mode as they  refinements of Joerg/ESR conversion can continue to run in read-only mode as they
 do today.  This means the "switch" is a few hours only for:  do today.  This means the "switch" is a few hours only for:
   
 ** cvs goes read only  1. cvs goes read only
 ** history from last git conversion pull until now is appended  2. history from last git conversion pull until now is appended
 ** cvs is turned off  3. cvs is turned off
 ** git is made available over ssh  4. git is made available over ssh
   

Removed from v.1.4  
changed lines
  Added in v.1.10


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb