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

Re: [PATCH v2] builtin/merge: allow --squash to commit if there are no conflicts

From
Edmundo Carmona Antoranz <eantoranz@gmail.com>
Date
Jul 18, 2019, 02:32 UTC
Message-ID
<CAOc6etY0tGNeekO7n5pqE_emtRytuSE77o1-fPetpzZPpkfMtA@mail.gmail.com>
In-Reply-To
<CAOc6etYM6DSDQ_H=eJs1xuGU9a83kTe2-vEy9+FEgHobT77_Eg@mail.gmail.com>

On Wed, Jul 17, 2019 at 6:41 PM Edmundo Carmona Antoranz <eantoranz@gmail.com> wrote:

>
>
> Does it make sense to keep this file in those two situations?
yes it does. disregard the question.
Previous: Edmundo Carmona Antoranz
Message 7 of 7 in “builtin/merge: allow --squash to commit if there are no conflicts”
  1. builtin/merge: allow --squash to commit if there are no conflictsEdmundo Carmona Antoranz, Jul 13, 2019
  2. Edmundo Carmona AntoranzJul 13, 2019
  3. Junio C HamanoJul 14, 2019
  4. Edmundo Carmona AntoranzJul 14, 2019
  5. Junio C HamanoJul 17, 2019
  6. Edmundo Carmona AntoranzJul 18, 2019
  7. Edmundo Carmona AntoranzJul 18, 2019

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.