fix(tmux): fix usage parsing with git master tmux

[dseomn]

This fixes usage parsing for the changes in
tmux/tmux@68ffe65

Tested against tmux 3.5a and faf2a448 (Merge branch 'obsd-master', 2025-05-12).

[akinomyoga]

The CI was fixed in #1380. @dseomn Could you rebase the head branch on top of the latest master?

[dseomn]

Sure, done.

[dseomn]

Do you need anything else from me on this?

Also, do you know if there's some way I could make stacked PRs so I can have more than one open at a time without creating merge conflicts?

[akinomyoga]

Do you need anything else from me on this?

We're just busy.

Also, do you know if there's some way I could make stacked PRs so I can have more than one open at a time without creating merge conflicts?

That one is what I really wanted for a long time... I currently have many stacked changes. I tried to reduce the number of stacking PRs by compressing multiple independent changes into a single PR, but then the other maintainers didn't like it. Then, I technically have dozens of PRs waiting in a single line...

[akinomyoga]

There don't seem to be others' opinions on this PR, so let's merge this now.

[dseomn]

Do you need anything else from me on this?

We're just busy.

Yup, thanks for merging.

Also, do you know if there's some way I could make stacked PRs so I can have more than one open at a time without creating merge conflicts?

That one is what I really wanted for a long time... I currently have many stacked changes. I tried to reduce the number of stacking PRs by compressing multiple independent changes into a single PR, but then the other maintainers didn't like it. Then, I technically have dozens of PRs waiting in a single line...

I looked into this a little bit, but didn't find much. If I have branches main <- branch-1 <- branch-2, I think I could create a PR to merge branch-1 into main in this repo, and a second PR to merge branch-2 into branch-1 in my fork. That doesn't seem ideal.