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

Re: [PATCH] Note the use of "rebase -i" to squash consecutive commits into one.

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 19, 2008, 03:32 UTC
Message-ID
<7vtzdhisre.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1219012340-23376-1-git-send-email-offby1@blarg.net>
This is missing sign-off.

More importantly, I do not think adding an extra illustration that starts talking about an example history that is _different_ from what was being discussed is a good idea. The end result lacks coherence and forces the reader to reset his mind for each example.

I'd suggest you to rewrite the example part that begins a few lines before you touched. Present the example "original" history with illustration first (and call it A---B---C---D---E---F---G, not QRSTU), and clarify the existing example of reordering the last 5 commits, and show the history after such reordering.

Then you talk about squashing, with before-and-after illustrations, but base that illustration on the same example history. That way, the reader has to understand the original scene only once to grok both examples.

Previous: Eric Hanchrow
Message 2 of 2 in “Note the use of "rebase -i" to squash consecutive commits into one.”
  1. Note the use of "rebase -i" to squash consecutive commits into one.Eric Hanchrow, Aug 17, 2008
  2. Junio C HamanoAug 19, 2008

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.