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

Should branches be objects?

From
NWNico Williams <nico@cryptonector.com>
Date
Jun 19, 2014, 21:37 UTC
Message-ID
<CAK3OfOiB0YWf25Hvvvqi+YBwu2V-gE-sjm7XrfE0p2zds4CE2Q@mail.gmail.com>
[I'm a list newbie here, but a git power user.]
If branches were objects...
 - one could see the history of branches, including
 - how commits were grouped when pushed/pulled (push 5 commits, and
the branch object will record that its head moved by those five
commits at once)
 - rebase history (git log <branch-object> -> better than git reflog!)
 - object transactional APIs would be used to update branches

Branch objects might be purely local, recording what was done in a local repo to a branch, but they might be pullable, to make branch history viewable in clones.

Just a thought,

Nico --

Next: Jonathan Nieder
Message 1 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.