Diff for /wikisrc/gitsofar.mdwn between versions 1.5 and 1.8

version 1.5, 2015/02/16 01:51:16 version 1.8, 2019/09/02 05:44:21
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)  * [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 26  slowly. Line 29  slowly.
   
 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 44  See above for CVS server provided if ong Line 46  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 56  Also see a great description of how Drag Line 62  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 86  Also using the dates for commits instead Line 94  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 96  Don't do anything weird like change hist Line 104  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 103  allowing non-"standard" actions. Line 114  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:
   

Removed from v.1.5  
changed lines
  Added in v.1.8


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