Re: [RFD] Making "git push [--force/--delete]" safer?

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 3, 2013, 19:50 UTC
Message-ID: <7vr4ffe83n.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CAF5DW8++sc2VYmdJEjbD_ue_wtDFj21vcyFzNWU0M+rAm2X0sQ@mail.gmail.com>

Jonathan del Strother <maillist@steelskies.com> writes:

> I'm struggling to think of instances where I wouldn't want this
> CAS-like behaviour.  Wouldn't it be better to make it the default when
> pushing, and allowing the current behaviour with "git push
> --blind-force" or something?

Not until we run this in the wild for a while and the mechanism proves to be useful without being too cumbersome to some population.

Then at a major version bump, we can start talking about enabling it by default, allowing people to selectively disable it.

$ 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.