BUG: Return of _logpmf

This fixes the bug mentioned in #4029
Do you just need to force push? (Note the `-f`).
```
git push -f https://github.com/helderc/scipy.git patch-1
```

I wrote the rest of this without reading your post carefully enough.  I'm going to leave it here, even though it sounds like you've gotten most of it sorted out already yourself.  Thanks for sticking with it through all of this.  I know it can be discouraging when contributing seems to require endless fighting with the tools rather than working on the code.

---------------------

I think @argriffing is right.  It I can see the spelling change commit under your master branch on github.  What has your work flow looked like?  Generally speaking the master branch in your repository isn't a useful thing.  What I do tends to look like this:

1. Create a clone of my scipy repository
`git clone https://github.com/ewmoore/scipy.git`

2. Add the main scipy repository as a remote
`git remote add upstream https://github.com/scipy/scipy.git`

3. Create a feature branch that tracks the master branch of the main scipy repository.
`git branch feature_name upstream/master`

4. Work, create commits, generally small and not necessarily fit for upstream 
`git add ...`
`git commit `

5. Rework commits with `git commit --amend` to fix up the last commit or 
`git rebase --interactive upstream/master` 
to fix up and squash a series of commits.

6. Push my changes to github
`git push https://github.com/ewmoore/scipy.git feature_name`
Ad this point, you can create your pull request, etc on github.

7.  If you need add a commit you can just do steps 4 and 6.  If you need to change something but want to keep it a single commit, you'll have to rewrite the history, step 5 and then force push to the same branch, that is use 
`git push -f https://github.com/ewmoore/scipy.git feature_name`  (note the `-f` here vs. in 6. above.) The force push is necessary because you are replacing the contents of the branch on github rather than adding commits to them.

Note that in all of this the master branch in my scipy repository is not used.

It looks to me as though you've somehow made all but the last change to both your patch-1 branch and your master branch.  This spelling change appears to have been committed to only the master branch.  Perhaps you had the wrong branch checked out when you made the commit?