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

Re: [PATCH v2] doc: improve readability of --rebase-merges in git-rebase

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 12, 2019, 04:18 UTC
Message-ID
<xmqqy2wlg22e.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20191111232137.GA29586@a.local>
Naveen Nathan <naveen@lastninja.net> writes:
> When --preserve-merges was deprecated in 427c3bd28a a sentence
> was introduced describing the difference between --rebase-merges and
> --preserve-merges which is a little unclear and difficult to parse.
> This patch improves readability while retaining original meaning.

I notice that the above also was rewritten since v1 and I think it is a very good change.

Thanks, will queue.
Previous: Naveen Nathan
Message 6 of 6 in “doc: improve readability of --rebase-merges in git-rebase”
  1. doc: improve readability of --rebase-merges in git-rebaseNaveen Nathan, Nov 10, 2019
  2. Johannes SchindelinNov 11, 2019
  3. Junio C HamanoNov 11, 2019
  4. Naveen NathanNov 11, 2019
  5. doc: improve readability of --rebase-merges in git-rebaseNaveen Nathan, Nov 11, 2019
  6. Junio C HamanoNov 12, 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.