A few things:
- The git repository tracking CVS works according to spec now (tracks pikefarm and trails it in less than 4 minutes at anytime for 7.8 and 7.9).
- There are two repositories:
git clone git://pike-git.lysator.liu.se/pike git clone git://pike-git.lysator.liu.se/pikex
The first repository contains only the official CVS branches. The second repository contains the official CVS branches *and* any experimental branches developers wish to advertise. As an example of one of the experimental branches, I created a branch called "testing" which is intended to be the last know stable snapshot of the development branch (7.9).
- As of now I would like to invite developers to ask for push/commit access to the pikex repository, in order to test and play around with committing directly to centralise git branches. The branches in pikex will be partly/selectively protected, depending on who wants to commit. There basically are several levels of protection: - People which I don't have the public key from cannot push at all. - For those that are able to push, the following restrictions will (currently) be enforced by the repository: + The official branches 0.5 ... 7.8 nt-tools extra_tests are protected and cannot be pushed into (currently). + Some branches are restricted to mere additions (regular commits). + Some branches cannot be committed to by all developers. + Some branches have no restrictions (i.e. can be created/removed or can even be destructively altered).
- If we ever move to git as the leading central repository, then the central repository will become pushable as well, but with severe restrictions (only regular commits, nothing destructive, no branch creation).
- In order to start granting access to pikex, I need public keys of developers.
After you've handed me the keys, pushing into the repository should become possible using a URL like:
git-pike@pike-git.lysator.liu.se:pikex
which actually is a shorthand for:
ssh://git-pike@pike-git.lysator.liu.se/~/pikex