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

Re: An alternate model for preparing partial commits

From
Stephen R. van den Berg <srb@cuci.nl>
Date
Jun 28, 2008, 09:30 UTC
Message-ID
<20080628093028.GA26745@cuci.nl>
David Jeske wrote:
>- I could supercede 2-commits with 1, effectively making the bad-commit
>disappear in the linear history. Users who already have the history, however,
>would be unaffected, because the start/end endpoints are the same.

Superseding does not work in git trees and is a disruptive operation to *all* commits following the point being superseded. Also, superseding preserves the startpoint, but *always* alters the endpoint.

I suggest you take a look at how a git-repository is stored and learn about how the SHA1-hashes interact with the stored repository.

-- 
Sincerely,
           Stephen R. van den Berg.

Heisenberg might have been here.
Message 1 of 1 in “Re: An alternate model for preparing partial commits”
  1. Stephen R. van den BergJun 28, 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.