DN42 registry
Find a file
yangybcy beba9e443c
1:add old key
2:change 172.23.150.0{0,64}/26 ---> 172.23.150.0{0,127}/25
3:delete AS4242428888
4:keep 172.23.190.0/26 (AS4242420198)
5:I lost the old secret-keys due to the failure of the old PC system.
2019-05-28 21:42:04 +08:00
data 1:add old key 2019-05-28 21:42:04 +08:00
utils/schema-check deleted unused file log.cphython-35.pyc 2018-06-03 16:42:07 +02:00
.gitignore Revert "Update 'data/dns/ripnet.dn42'" 2018-02-25 13:36:09 -05:00
check-my-stuff Revert "Update 'data/dns/ripnet.dn42'" 2018-02-25 13:36:09 -05:00
check-pol Revert "Update 'data/dns/ripnet.dn42'" 2018-02-25 13:36:09 -05:00
check-remote Revert "Update 'data/dns/ripnet.dn42'" 2018-02-25 13:36:09 -05:00
fmt-my-stuff Revert "Update 'data/dns/ripnet.dn42'" 2018-02-25 13:36:09 -05:00
install-commit-hook Revert "Update 'data/dns/ripnet.dn42'" 2018-02-25 13:36:09 -05:00
README.md Revert "Update 'data/dns/ripnet.dn42'" 2018-02-25 13:36:09 -05:00

Tips for a successful Pull Request

  1. Squash your commits -- Keep the changes simple to read.
  2. Run the schema check -- Make sure the changes are valid! Run ./check-my-stuff YOUROWN-MNT
  3. BONUS: install the commit hook! Run ./install-commit-hook YOUROWN-MNT
  4. Sign your commit -- Makes it easier to verify.
  5. Bonus: add your pgp fingerprint to your MNT auth: pgp-fingerprint <pgp-fingerprint> [See XUU-MNT example]
  6. ???
  7. Profit!