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

Re: [PATCH v2] rebase -r: always reword merge -c

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
May 3, 2019, 09:23 UTC
Message-ID
<nycvar.QRO.7.76.6.1905031123150.45@tvgsbejvaqbjf.bet>
In-Reply-To
<20190502102249.9071-1-phillip.wood123@gmail.com>
Hi Phillip,
On Thu, 2 May 2019, Phillip Wood wrote:
Show 8 quoted lines
> From: Phillip Wood <phillip.wood@dunelm.org.uk>
>
> If a merge can be fast-forwarded then make sure that we still edit the
> commit message if the user specifies -c. The implementation follows the
> same pattern that is used for ordinary rewords that are fast-forwarded.
>
> Signed-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>
> ---
ACK!

Thank you, Dscho

Previous: Phillip WoodNext: Johannes Schindelin
Message 6 of 8 in “rebase -r: always reword merge -c”
  1. rebase -r: always reword merge -cPhillip Wood, Apr 26, 2019
  2. Johannes SchindelinApr 29, 2019
  3. Phillip WoodApr 30, 2019
  4. Johannes SchindelinApr 30, 2019
  5. rebase -r: always reword merge -cPhillip Wood, May 2, 2019
  6. Johannes SchindelinMay 3, 2019
  7. Johannes SchindelinMay 17, 2019
  8. Junio C HamanoMay 19, 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.