> * mm/git-pm-try-catch-syntax-fix (2022-10-17) 1 commit > - Git.pm: add semicolon after catch statement > > Fix a longstanding syntax error in Git.pm error codepath. > > Will merge to 'next'?? > source: <20221016212236.12453-2-michael@xxxxxxxxxxxx> I am not totally sure what these question marks mean, but I'm happy for this to go to next, for what it's worth. (There was an outstanding question about the general behavior of Git.pm in bare unsafe repositories, but I certainly am not planning to solve it in this series.) Thanks! -- Michael McClimon michael@xxxxxxxxxxxx