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

Re: How to force a push to succeed?

From
Johannes Sixt <j6t@kdbg.org>
Date
Aug 23, 2017, 17:06 UTC
Message-ID
<6d9c7dd4-f1ad-8f5b-1e7b-2dcc5b9baf7e@kdbg.org>
In-Reply-To
<CAH8yC8=HuAZ0tJbRGnp83-Th5OkQ0-cdSOBrMU23y6NyB0Ax3g@mail.gmail.com>
Am 23.08.2017 um 00:26 schrieb Jeffrey Walton:
> You know, I look at how fucked up yet another simple workflow is, and
> all I can do is wonder. It is absolutely amazing. Its like the project
> goes out of its way to make simple tasks difficult.

No, no. So simple your task might look, in the end you have LOST DATA! It is a design goal of Git to make it difficult to lose data.

-- Hannes
Previous: Jeffrey WaltonNext: Jonathan Nieder
Message 6 of 8 in “How to force a push to succeed?”
  1. Jeffrey WaltonAug 22, 2017
  2. Stefan BellerAug 22, 2017
  3. Jeffrey WaltonAug 22, 2017
  4. Jeffrey WaltonAug 22, 2017
  5. Jeffrey WaltonAug 22, 2017
  6. Johannes SixtAug 23, 2017
  7. Jonathan NiederAug 23, 2017
  8. Kevin DaudtAug 23, 2017

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.