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

Re: Should branches be objects?

From
NWNico Williams <nico@cryptonector.com>
Date
Jun 20, 2014, 00:31 UTC
Message-ID
<CAK3OfOhC4krFUDJ9nOzMfhkHjX_76L2k+tdEsbqcAzWDseeNAg@mail.gmail.com>
In-Reply-To
<CAK3OfOjnYXxhWT7Vp-0Pcb=F8ze6wJnqSm1_LW0Zp1FmYZfUEg@mail.gmail.com>

Another thing is that branches as objects could store a lot more information, like:

 - the merge-base and HEAD for a rebase (and the --onto)
 - the interactive rebase plan!  (and diffs to what would have been
the non-interactive plan)
 - the would-be no-op non-interactive rebase plan post rebase (again,
so elucidate what commit splitting and such things occurred during a
rebase)

Nico --

Previous: Nico WilliamsNext: Jonathan Nieder
Message 4 of 6 in “Should branches be objects?”
  1. Nico WilliamsJun 19, 2014
  2. Jonathan NiederJun 19, 2014
  3. Nico WilliamsJun 20, 2014
  4. Nico WilliamsJun 20, 2014
  5. Jonathan NiederJun 20, 2014
  6. Jeff KingJun 20, 2014

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.