23:23:05drmeisterI can't remember a single instance where I have been involved in a submodule update that worked smoothly. I think this one just had the bad luck of happening when I found that cleavir bug.
23:23:23drmeisterThen I edit something in the submodule when you had updated the submodule.
23:23:38Bikeok yeah so what was the cleavir bug, because i just reset it to where i had it.
23:24:10drmeisterThere is a :form keyword argument to a condition that shouldn't be there. Or a form slot needs to be added to a condition.
23:24:38Bikeright. yeah. i think beach said he fixed that?
23:27:48drmeisterSo anyone who pulls this stuff has to do this?
23:28:02Bikewhen you run that, it tells git to reset the submodule to whatever commit hash is in the file
23:29:12Bikeand it does not do that automatically. so, when you pull my changes, you get the updated submodule hash, but the actual files on disk are the old ones. because of the rebasing, git interprets this as the submodule having been updated, or changed, from the history's hash