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

Re: RFD: best way to automatically rewrite a git DAG as a linear history?

From
Jon Seymour <jon.seymour@gmail.com>
Date
Feb 21, 2010, 23:04 UTC
Message-ID
<2cfc40321002211504o28069d16h4b9d1ef2230d03fe@mail.gmail.com>
In-Reply-To
<32541b131002191905u59a90866he0a38dfc661d45d2@mail.gmail.com>
On Sat, Feb 20, 2010 at 2:05 PM, Avery Pennarun <apenwarr@gmail.com> wrote:
Show 7 quoted lines
> On Fri, Feb 19, 2010 at 9:25 PM, Jon Seymour <jon.seymour@gmail.com> wrote:
>> (A hammer is, of course, a reasonably good tool for making things flat
>> although it does tend to break things along the way).
>
> Nice analogy.  Well, thanks for the clarification and best of luck in
> your slightly crazy project :)
>

Thank you - FWIW, it is shaping up very well. In turns out that in cases where the original merge was resolved in favour of the conflict, the compensation can be squashed with the compensated commit - effectively bring the eventual resolution forward in time.

This is so, so cool.
jon.
Previous: Avery PennarunNext: Jon Seymour
Message 10 of 11 in “RFD: best way to automatically rewrite a git DAG as a linear history?”
  1. Jon SeymourFeb 18, 2010
  2. Jeff KingFeb 18, 2010
  3. Avery PennarunFeb 18, 2010
  4. Jon SeymourFeb 19, 2010
  5. Avery PennarunFeb 19, 2010
  6. Jon SeymourFeb 19, 2010
  7. Avery PennarunFeb 19, 2010
  8. Jon SeymourFeb 20, 2010
  9. Avery PennarunFeb 20, 2010
  10. Jon SeymourFeb 21, 2010
  11. Jon SeymourFeb 21, 2010

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.