version 1.1, 2015/02/01 02:25:27
|
version 1.2, 2015/02/01 02:30:33
|
Line 1
|
Line 1
|
== 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: |
### Low memory hosts: |
* http://mail-index.netbsd.org/tech-repository/2015/01/08/msg000520.html |
|
|
* [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 |
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 |
protocol used. Over http I am able to get a full clone with all history on a |
Line 21 git is slow during 'status' by default s
|
Line 22 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. |
|
|
=== CVS in parallel |
### CVS in parallel |
|
|
I do not think this is a good idea and do not plan to advocate for it. |
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 |
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. |
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 |
One-shot to create the new True Source. I don't think there will be many cvs |
hold-outs. |
hold-outs. |
|
|
See above for CVS server provided if ongoing conversion is really desired. |
See above for CVS server provided if ongoing conversion is really desired. |
|
|
=== existing cvs dependencies |
### existing cvs dependencies |
|
|
TBD |
TBD |
|
|
=== How should NetBSD be setup |
### How should NetBSD be setup |
|
|
High level- private box for write master using ssh, any number of additional |
High level- private box for write master using ssh, any number of additional |
systems with read-only mirrors over http:// and git:// |
systems with read-only mirrors over http:// and git:// |
|
|
Also see a great description of how DragonflyBSD is setup: |
Also see a great description of how DragonflyBSD is setup: |
http://lists.dragonflybsd.org/pipermail/users/2015-January/207421.html |
[dfbsd server setup](http://lists.dragonflybsd.org/pipermail/users/2015-January/207421.html) |
http://lists.dragonflybsd.org/pipermail/users/2015-January/207422.html |
[dfbsd workflows](http://lists.dragonflybsd.org/pipermail/users/2015-January/207422.html) |
http://lists.dragonflybsd.org/pipermail/users/2015-January/207424.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 |
git should fit into NetBSD src/tools easily. I have not personally tested |
cross compilation. |
cross compilation. |
|
|
=== workflows |
### workflows |
|
|
See DragonflyBSD examples given above |
See DragonflyBSD examples given above |
|
|
There are many many workflows supported in git. For the most part I think |
There are many many workflows supported in git. For the most part I think |
Line 65 for a friendly developer to add as an or
|
Line 72 for a friendly developer to add as an or
|
(git origin add future-developer http://example.com/~greatguy/src.git) |
(git origin add future-developer http://example.com/~greatguy/src.git) |
|
|
|
|
=== log message formats |
### log message formats |
|
|
Try to references named branches instead of sha-1's |
Try to references named branches instead of sha-1's |
Also using the dates for commits instead of commit id's |
Also using the dates for commits instead of commit id's |
|
|
=== how to convert |
### how to convert |
|
|
ESR? |
ESR? |
|
|
=== No lock-in |
### No lock-in |
|
|
I am unable to anticipate the next generation of SCM. |
I am unable to anticipate the next generation of SCM. |
Don't do anything weird like change history and we should be fine. |
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 |
Maybe when we have 30 years of project history it will be time to consider |
restructuring the project. :) |
restructuring the project. :) |
|
|
=== Who, When, and How Long? |
### Who, When, and How Long? |
|
|
* ESR/Joerg - convert |
* ESR/Joerg - convert |
* sometime, eventually, maybe |
* sometime, eventually, maybe |
* unknown |
* unknown |