Re: [RFC] branch: delete gone-upstream branches only when proven merged into a named ref
- From
D. Ben Knoble <ben.knoble@gmail.com>
- Date
- Oct 24, 2026, 13:18 UTC
- Message-ID
- <CALnO6CAd62NqWMw66UT7mDuM71rcSBFidrr5f+PfR2jA9D9v=g@mail.gmail.com>
- In-Reply-To
- <CAHwyqnWJOk9FCGkPi8yWOFq5vr-CMWNhn=wBAifx9Gfn+1bMzA@mail.gmail.com>
On Thu, Oct 22, 2026 at 1:52 PM Harald Nordgren <haraldnordgren@gmail.com> wrote:
Show 27 quoted lines
> > On Thu, Oct 22, 2026 at 7:14 PM Ben Knoble <ben.knoble@gmail.com> wrote: > > > > > Le 22 oct. 2026 à 10:39, Harald Nordgren <haraldnordgren@gmail.com> a écrit : > > >> > > >> I would much rather see more --option=value,value,value syntaxes, like > > >> > > >> git branch --delete-merged='origin/*,into:origin/master' > > > > > > This feels completely chaotic to me and becomes a kitchen sink :) > > > > But is it better or worse than the kitchen sink of > > > > git branch --delete-merged origin/* --into origin/master […] > > > > ? Hm. I suppose if you didn’t like commas, we could allow > > repeating the option to « stack » instead of replacing. > > > > But I get the feeling that’s not what you took issue with ;) > > No, this is the part I take issue with: > > --delete-merged=into:origin/master > > It feels akin to hacking some code into the arg like a > > find . -exec something
Well, I find it more composable than tacking on additional modifiers via --long-options (which incidentally make the synopsis more complicated, and add lots of "this option only makes sense in this context" checks)---that "context-sensitive" nature seems to me to make our interface quite a bit more confusing. See the "INCOMPATIBLE OPTIONS" section of git-rebase, for example!
-- D. Ben Knoble