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

Merging commits together into a super-commit

From
EKEugine Kosenko <eugine.kosenko@gmail.com>
Date
May 11, 2007, 12:41 UTC
Message-ID
<9909dee80705110541m13c4035tc8338e179d6bec9b@mail.gmail.com>
In-Reply-To
<9909dee80705110537j7e6d1426p7723c110c0a2c667@mail.gmail.com>
2007/5/11, Alex Riesen <raa.lkml@gmail.com>:
> And it is not enough. Authorship information is lost.

If one dare to make such super-commit, he would be the author of the whole couple of changes.

> And you have to be damn sure the "branch" starts directly at HEAD,
> otherwise everything HEAD..branch is lost. It is complex
> if you want it right.
I used to make git-rebase to add extra commits after this.
Previous: Alex RiesenNext: Jan Hudec
Message 3 of 4 in “Re: Merging commits together into a super-commit”
  1. linux@horizon.comMay 10, 2007
  2. Alex RiesenMay 11, 2007
  3. Merging commits together into a super-commitEugine Kosenko, May 11, 2007
  4. Jan HudecMay 12, 2007

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.