I merged #402 onto master at a point after #472 and resolved the conflicts. The merge is at 5d6e87b. In testing the importer I ran into some rate limiting issues from Posterous and updated the code to handle those. (sleep for retry_after + 1 seconds)
retry_after + 1
When I tried to rebase master onto #402 git informed me that the branches had diverged. I would have needed to --force the pushto GitHub and I'm not sure what would have happend to the PR at that point. I am not skilled enough at git to know how I could have done this any differently so I created a new branch and PR instead.
If it would be better to --force the existing PR please let me know the best way for me to do that. :) Otherwise I am hoping this PR merges cleanly.
Change to new posterous API
YAML front matter fix, cleaned up slug generation, added tags and sto…
…re some posterous information from the original post.
Merge remote-tracking branch 'origin/alagu-master' into alagu-postero…
Conflict created due to #472.
Handle Posterous rate limiting
Is there a way for me to use this script now, so I don't have to wait for it to be merged?
If that's possible, any advice on how to do it would be appreciated.
I have pulled changes and updated in pull request 651
Updated in #651.