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

Re: Should branches be objects?

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jun 19, 2014, 23:46 UTC
Message-ID
<20140619234614.GY8557@google.com>
In-Reply-To
<CAK3OfOiB0YWf25Hvvvqi+YBwu2V-gE-sjm7XrfE0p2zds4CE2Q@mail.gmail.com>
Hi,
Nico Williams wrote:
>  - one could see the history of branches, including

Interesting. 'git log -g' is good for getting that information locally, but the protocol doesn't have a way to get it from a remote server so you have to ssh in. Ronnie (cc-ed) and I were talking recently about whether it would make sense to update git protocol to have a way to get at the remote reflogs more easily --- would that be useful to you?

>  - 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)
The reflog on the server (if enabled) records this.
>  - rebase history (git log <branch-object> -> better than git reflog!)
The local reflog ('git log -g <branch>') records this.
>  - object transactional APIs would be used to update branches
Ronnie's recent ref-transaction code does this.

Thanks and hope that helps, Jonathan

Previous: Nico WilliamsNext: Nico Williams
Message 2 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.