All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Harald Nordgren <haraldnordgren@gmail.com>
Subject: Re: [PATCH] branch: let --delete-merged default to every upstream
Date: Fri, 02 Oct 2026 10:11:23 -0700	[thread overview]
Message-ID: <xmqq8q4gxc1w.fsf@gitster.g> (raw)
In-Reply-To: <pull.2428.git.git.1790960147943.gitgitgadget@gmail.com> (Harald Nordgren via GitGitGadget's message of "Fri, 02 Oct 2026 16:55:47 +0000")

"Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com> writes:

> From: Harald Nordgren <haraldnordgren@gmail.com>
>
> Cleaning up every branch whose work has landed upstream required
> typing '*/*' as the pattern.

This description and what the code actually does contradict with
each other, I wonder?

> Let a bare "git branch --delete-merged" consider every upstream. As
> with "--merged" without a commit, this applies only when the option
> comes last, so "git branch --dry-run --delete-merged" previews the
> cleanup.

There are many options ('--merged', '--no-merged', '--contains',
'--no-contains', '--unset-upstream', '--edit-description') that
default to the current branch, which is a very natural thing within
the context of git.  Is defaulting to '**' is a good comparison to
them?  I dunno.

> +			.defval = (intptr_t) "**",
> +		},

  reply	other threads:[~2026-10-02 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 16:55 [PATCH] branch: let --delete-merged default to every upstream Harald Nordgren via GitGitGadget
2026-10-02 17:11 ` Junio C Hamano [this message]
2026-10-04  8:34 ` [PATCH v2] " Harald Nordgren via GitGitGadget
2026-10-04  9:55 ` [PATCH] " Phillip Wood
2026-10-04 13:16   ` Harald Nordgren
2026-10-04 18:42     ` Phillip Wood
2026-10-04 18:50       ` Harald Nordgren
2026-10-05  4:27       ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq8q4gxc1w.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=haraldnordgren@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.