diff --git a/_posts/2016-03-05-overview-and-logs-for-the-dev-meeting-held-on-2016-03-05.md b/_posts/2016-03-05-overview-and-logs-for-the-dev-meeting-held-on-2016-03-05.md index 9bdf3591..5b6506b1 100644 --- a/_posts/2016-03-05-overview-and-logs-for-the-dev-meeting-held-on-2016-03-05.md +++ b/_posts/2016-03-05-overview-and-logs-for-the-dev-meeting-held-on-2016-03-05.md @@ -45,7 +45,7 @@ author: gingeropolous **\** we have to implement some sort of migration system **\** we can't expect people in production to keep dropping and re-syncing **\** so that would stall it being merged -**\** hi, sorry I'm late. our experience with blockchain_import indicates migration will be slow +**\** hi, sorry I'm late. our experience with blockchain\_import indicates migration will be slow **\** also, migration won't take place until after things settle with the db changes and testing. **\** development is ongoing here https://github.com/warptangent/bitmonero/branches in the exp/performance branch **\** hyc: well at the very least we need to detect that the current DB isn't what we expect, and that it must be converted or redownloaded @@ -115,7 +115,7 @@ author: gingeropolous **fluffypony** ponders **\** oh yes **\** I would prefer new wallets don't auto-refresh, but I understand why it was added -**\** net_skeleton become Fossa which became Mongoose +**\** net\_skeleton become Fossa which became Mongoose **\** which needs to become gone ? **\** yes **\** the only licenses they have available are GPL and a commercial license