version 1.2, 2015/02/01 02:30:33
|
version 1.7, 2017/09/22 10:37:52
|
Line 22 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. |
|
|
|
*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. |
|
|
### 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. |
Line 37 See above for CVS server provided if ong
|
Line 43 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 |
|
|
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:<br> |
[dfbsd server setup](http://lists.dragonflybsd.org/pipermail/users/2015-January/207421.html) |
[dfbsd server setup](http://lists.dragonflybsd.org/pipermail/users/2015-January/207421.html)<br> |
[dfbsd workflows](http://lists.dragonflybsd.org/pipermail/users/2015-January/207422.html) |
[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) |
[dfbsd config](http://lists.dragonflybsd.org/pipermail/users/2015-January/207424.html)<br> |
|
|
### how to install |
### how to install |
|
|
Line 74 for a friendly developer to add as an or
|
Line 84 for a friendly developer to add as an or
|
|
|
### log message formats |
### log message formats |
|
|
Try to references named branches instead of sha-1's |
Try to references named branches/tags 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? |
https://github.com/netbsd/ |
|
|
### No lock-in |
### No lock-in |
|
|
Line 89 Don't do anything weird like change hist
|
Line 99 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 |
|
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 |
* 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: |
|
|
|
1. cvs goes read only |
|
2. history from last git conversion pull until now is appended |
|
3. cvs is turned off |
|
4. git is made available over ssh |
|
|