git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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
Previous: D. Ben Knoble
Message 15 of 15 in “[RFC] branch: delete gone-upstream branches only when proven merged into a named ref”
  1. DonQuinleoneOct 17, 2026
  2. D. Ben KnobleOct 22, 2026
  3. Harald NordgrenOct 22, 2026
  4. D. Ben KnobleOct 24, 2026
  5. Harald NordgrenOct 24, 2026
  6. D. Ben KnobleOct 24, 2026
  7. Harald NordgrenOct 22, 2026
  8. Ben KnobleOct 22, 2026
  9. Harald NordgrenOct 22, 2026
  10. Harald NordgrenOct 22, 2026
  11. D. Ben KnobleOct 24, 2026
  12. DonQuinleoneOct 24, 2026
  13. Harald NordgrenOct 24, 2026
  14. D. Ben KnobleOct 27, 2026
  15. D. Ben KnobleOct 24, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.