{"thread":{"id":"14199","subject":"Re: An alternate model for preparing partial commits","startedAt":"2008-06-28T09:30:28Z","lastAt":"2008-06-28T09:30:28Z","messageCount":1,"participants":["Stephen R. van den Berg"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"81548","messageId":"20080628093028.GA26745@cuci.nl","threadId":"14199","inReplyTo":null,"subject":"Re: An alternate model for preparing partial commits","fromName":"Stephen R. van den Berg","fromEmail":"srb@cuci.nl","sentAt":"2008-06-28T09:30:28Z","receivedAt":"2008-06-28T09:30:28Z","isPatch":false,"sender":{"key":"srb@cuci.nl","avatar":"https://gravatar.com/avatar/f75389059e827634d38e9df2a9b6ecbd50028b5a454442efa1c7205b7ff29c6a?d=mp&s=160"},"body":"David Jeske wrote:\n>- I could supercede 2-commits with 1, effectively making the bad-commit\n>disappear in the linear history. Users who already have the history, however,\n>would be unaffected, because the start/end endpoints are the same.\n\nSuperseding does not work in git trees and is a disruptive operation to\n*all* commits following the point being superseded.\nAlso, superseding preserves the startpoint, but *always* alters the\nendpoint.\n\nI suggest you take a look at how a git-repository is stored and learn\nabout how the SHA1-hashes interact with the stored repository.\n-- \nSincerely,\n           Stephen R. van den Berg.\n\nHeisenberg might have been here.\n"}]}