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

Re: [PATCH 0/2] rebase --recreate-merges --keep-empty: don't prune empty

From
PWPhillip Wood <phillip.wood@talktalk.net>
Date
Mar 20, 2018, 18:40 UTC
Message-ID
<e306f33a-3cd9-b753-ed61-66b7ff614087@talktalk.net>
In-Reply-To
<nycvar.QRO.7.76.6.1803201639540.55@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz>
On 20/03/18 15:42, Johannes Schindelin wrote:
Show 18 quoted lines
> Hi Phillip,
> 
> On Tue, 20 Mar 2018, Phillip Wood wrote:
> 
>> From: Phillip Wood <phillip.wood@dunelm.org.uk>
>>
>> These patches apply on top of js/rebase-recreate-merge. They extend
>> the --keep-empty fix from maint [1] to work with --recreate-merges.
> 
> As indicated in another reply, I'd rather rebase the --recreate-merges
> patches on top of your --keep-empty patch series. This obviously means
> that I would fold essentially all of your 2/2 changes into my
> "rebase-helper --make-script: introduce a flag to recreate merges"
> 
> The 1/2 (with s/failure/success/g) would then be added to the
> --recreate-merges patch series at the end.
> 
> Would that be okay with you?
Yes, that's fine, it would give a clearer history
Best Wishes
Phillip
Previous: Johannes SchindelinNext: Junio C Hamano
Message 6 of 9 in “rebase --recreate-merges --keep-empty: don't prune empty”
  1. 0/2 rebase --recreate-merges --keep-empty: don't prune emptyPhillip Wood, Mar 20, 2018
  2. 2/2 rebase --recreate-merges --keep-empty: don't prune empty commitsPhillip Wood, Mar 20, 2018
  3. Johannes SchindelinMar 20, 2018
  4. 1/2 add failing test for rebase --recreate-merges --keep-emptyPhillip Wood, Mar 20, 2018
  5. Johannes SchindelinMar 20, 2018
  6. Phillip WoodMar 20, 2018
  7. Junio C HamanoMar 20, 2018
  8. Phillip WoodMar 22, 2018
  9. Junio C HamanoMar 22, 2018

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.