[19:56:45] <roguelazer>	 git somewhere recently (perhaps 2.35) started doing silly things when merging when the user has enabled `submodule.recurse` in their gitconfig; aside from telling users "don't do that", has anyone got any good thoughts on how to fix this?
[19:57:01] <roguelazer>	 I was thinking about patching arcanist to just always pass `-c submodule.recurse=0` when invoking git, but I'm worried that might be too big of a hammer
[20:04:57] <roguelazer>	 https://we.phorge.it/P4 is what I've got so far, heh
[20:42:00] <cspeckrun[m]>	 Could you describe the issue further? I don’t follow what problem is occurring
[23:41:12] <roguelazer>	 if you set the git config option `submodule.recurse` globally and then `arc land` a branch that only includes a submodule change, the change gets lost
[23:41:36] <roguelazer>	 something about the sequence of commands arcanist runs results in the `git checkout` getting recursed into the submodule, so the change goes away during the rebase step in the squash land strategy
[23:42:07] <roguelazer>	 disabling submodule.recurse fixes it, but I can't really guarantee that all of my users are going to do that (and it's also super-handy to have submodule.recurse on so you don't have to remember to manually do submodule ops)
[23:42:25] <roguelazer>	 so my proposal is that arcanist should probably always disable `submodule.recurse` (and any other options that significnatly change git's behavior) prior to invoking git