phdsg vn chfhn

seems fixed as andrew said: pluk is still weird. never the same offset and only happens when pluk is triggered from the program change. first trig-in usually brings it back...

do we check if the code builds?

@AndrewBelt does "branch" in .gitmodules have to point to the specific commit we checked out in the repo?

yea, that worked for the previous PRs i did. but with the moDllz i had a problem... did what you just said. entered repo, pulled, checked out the commit... after...

ah. this repo was already bumped to 0.6.1 before (but not yet made available)... will take another look.

anyways, for the future: how do we deal with situations like that @AndrewBelt ? when a dev requests multiple updates between builds, one version bump per request or one per...

ok, tried once more to update the moDllz repo... starting from clean working tree `cd repos/moDllz`, `git pull`, `git checkout 59c14cf`, `cd ../..` gets me here: ``` $ git status...

``` $ git status On branch master Your branch is ahead of 'origin/master' by 5 commits. (use "git push" to publish your local commits) Changes not staged for commit: (use...

``` $ git status HEAD detached at 59c14cf Changes not staged for commit: (use "git add/rm ..." to update what will be committed) (use "git checkout -- ..." to discard...

is this a capitalization thing?