Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Harald Nordgren <haraldnordgren@gmail.com>
Cc: Harald Nordgren via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 2/2] branch: protect local upstreams from -d
Date: Wed, 26 Aug 2026 07:37:59 -0700	[thread overview]
Message-ID: <xmqqfr01j6bc.fsf@gitster.g> (raw)
In-Reply-To: <CAHwyqnXjO6Cv50BVjJjW939A06-bQtcA2uf0Cwk+xuoc2Gh_LA@mail.gmail.com> (Harald Nordgren's message of "Wed, 26 Aug 2026 08:56:51 +0200")

Harald Nordgren <haraldnordgren@gmail.com> writes:

> Hmm, it makes sense what you are saying, but I could have sworn that
> you asked for this (likely some very different version from this) when
> I was working on delete-merged, i.e. to extend branch protections to
> '-d' as well. Phillip brought it up recently as well. Maybe I
> misunderstood.

It is more likely that I misstated.  I do appreciate that we now
have a machinery that allows us to offer an "improved" protection
feature that may be "better" than 'branch -d' to users.  It is a
different matter in what shape we offer the feature while balancing
the need to avoid breaking established end-user workflow.

Thanks for working on this topic.


  parent reply	other threads:[~2026-08-26 14:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 21:25 [PATCH 0/2] branch: -d protects upstream branches Harald Nordgren via GitGitGadget
2026-08-25 21:25 ` [PATCH 1/2] branch: move stacked branch helpers Harald Nordgren via GitGitGadget
2026-08-25 21:25 ` [PATCH 2/2] branch: protect local upstreams from -d Harald Nordgren via GitGitGadget
2026-08-25 21:59   ` Junio C Hamano
2026-08-26  6:56     ` Harald Nordgren
2026-08-26  8:46       ` Tuomas Ahola
2026-08-26  9:20         ` Harald Nordgren
2026-08-26 14:37       ` Junio C Hamano [this message]
2026-08-27  5:19   ` Elijah Newren

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=xmqqfr01j6bc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox