--- wikisrc/gitsofar.mdwn 2015/02/01 02:25:27 1.1 +++ wikisrc/gitsofar.mdwn 2015/02/16 01:44:18 1.4 @@ -1,9 +1,10 @@ -== NetBSD with git so far +## NetBSD with git so far -http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html +[core statement on vcs](http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html) -=== Low memory hosts: -* http://mail-index.netbsd.org/tech-repository/2015/01/08/msg000520.html +### Low memory hosts: + +* [tuning for git on low memory](http://mail-index.netbsd.org/tech-repository/2015/01/08/msg000520.html) git appears to have slightly different memory characteristics depending on the protocol used. Over http I am able to get a full clone with all history on a @@ -21,34 +22,46 @@ git is slow during 'status' by default s change. It will produce a warning with tunable options if the command runs slowly. -=== CVS in parallel +** Update +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, +work on my 512 system. I'm pretty sure a 256 + swap without any special tuning +would also work. + +### CVS in parallel + I do not think this is a good idea and do not plan to advocate for it. Git does have a cvs server built-in but I have not taken the time to set it up for testing because it is slightly involved and I don't see the purpose. -=== Conversion +### Conversion + One-shot to create the new True Source. I don't think there will be many cvs hold-outs. See above for CVS server provided if ongoing conversion is really desired. -=== existing cvs dependencies +### existing cvs dependencies + TBD -=== How should NetBSD be setup +### How should NetBSD be setup + High level- private box for write master using ssh, any number of additional systems with read-only mirrors over http:// and git:// -Also see a great description of how DragonflyBSD is setup: -http://lists.dragonflybsd.org/pipermail/users/2015-January/207421.html -http://lists.dragonflybsd.org/pipermail/users/2015-January/207422.html -http://lists.dragonflybsd.org/pipermail/users/2015-January/207424.html +Also see a great description of how DragonflyBSD is setup:
+[dfbsd server setup](http://lists.dragonflybsd.org/pipermail/users/2015-January/207421.html)
+[dfbsd workflows](http://lists.dragonflybsd.org/pipermail/users/2015-January/207422.html)
+[dfbsd config](http://lists.dragonflybsd.org/pipermail/users/2015-January/207424.html)
+ +### how to install -=== how to install git should fit into NetBSD src/tools easily. I have not personally tested cross compilation. -=== workflows +### workflows + See DragonflyBSD examples given above There are many many workflows supported in git. For the most part I think @@ -65,21 +78,39 @@ for a friendly developer to add as an or (git origin add future-developer http://example.com/~greatguy/src.git) -=== log message formats -Try to references named branches instead of sha-1's +### log message formats + +Try to references named branches/tags instead of sha-1's Also using the dates for commits instead of commit id's -=== how to convert +### how to convert + ESR? -=== No lock-in +### No lock-in + I am unable to anticipate the next generation of SCM. Don't do anything weird like change history and we should be fine. Maybe when we have 30 years of project history it will be time to consider restructuring the project. :) -=== Who, When, and How Long? +--- + +I think this is less a function of the tool and more a function of the project not +allowing non-"standard" actions. + +### Who, When, and How Long? + * ESR/Joerg - convert * sometime, eventually, maybe -* unknown +* assumptions/proposal: + +Assuming conversion starting from date(x) to freeze(y) is relatively easy, the +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: + +** cvs goes read only +** history from last git conversion pull until now is appended +** cvs is turned off +** git is made available over ssh