Tim, I assume this is good stuff. However, I'm guessing you meant to PR 1 commit, not 72. This branch has all of the "merge" stuff we already talked about as making the PR-evaluator/merge's life hard, along with a new even-larger "merge" commit: the penultimate one changes 361 files.

If you'd like to make things easier for everyone (especially you!) going forward, and use git like a pro, read on. If this is too much of a diversion from things that are more important to you, let me know and I'll pull out what I can from the PR as currently is. If you have questions about this stuff, feel free to join IRC on irc.perl.org/#pdl.

I've brought the PDLPorter repo's hainest-assgn_badflag up to date by rebasing it against current master, and force-pushed it. What I'd like you to do is make your repo's assgn_badflag branch be up to date with that, something like:

git checkout -b assgn_badflag-rebased master
git pull https://github.com/PDLPorters/PDL.git hainest-assgn_badflag # get latest rebased version
git checkout assgn_badflag
git rebase -i assgn_badflag-rebased # the -i lets you look at the list and make sure it's what you expect
# now make there be any extra commits you want
git push -f # update your copy of the branch, which will magically update the PR

Please put a comment on here when you've done this since github won't tell me when you've updated it.

Ah! No, I definitely didn't mean to submit 72 commits! I don't normally work with rebased repos, so I greatly appreciate you outlining how to use that. I have received notice that the assgn_badflag branch was merged with master, so I am assuming you took care of that. If so, thanks!

Whatever notice you received was incorrect. It is not merged, as we are too close to a release for this kind of late change. However I am very keen for this work to be completed and for it to improve a near-future release! Once again, please action my suggestions above and fix up your work so it is of use.