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

Re: policy and mechanism for less-connected clients

From
RBRaimund Bauer <ray007@gmx.net>
Date
Jun 25, 2008, 20:12 UTC
Message-ID
<1214424774.6570.21.camel@doriath>
In-Reply-To
<alpine.LNX.1.00.0806251421520.19665@iabervon.org>
On Wed, 2008-06-25 at 15:17 -0400, Daniel Barkalow wrote:
Show 5 quoted lines
> You have a fundamental misconception about git's data model. A commit 
> doesn't have a particular branch it is on. There is only the DAG, where 
> each node is a commit that is structured identically to all of the other 
> commits. Branches pick out particular nodes in the DAG at particular 
> times.

But a branch in repository also has a local history. The ref-log. And git could use that to produce a distributed branch-history.

<wishful thinking>

A developer prepares a series of commits in a local branch to push to the server. On the server the ref-log of a branch gets updated with a new entry for each push, and other developers pulling from the server get the servers ref-log as ref-log of their remote tracking branch and can see the push-points there.

Those push-points seem to be somehow more important than other commits - there was a reason for the first developer to push right this branch tip, right? Seems like valuable (optional) information to me.

</wishful thinking>
> It therefore doesn't make any sense to ask if a commit is directly hanging 
> off of master. If your local branch is up to date, and you commit, your 
> commit's parent is the current master. If you now check out master and 
> merge your local branch, master gets the same (non-merge) commit.
Check if the commit is in master's ref-log?

regards, Ray

Previous: Daniel Barkalow
Message 6 of 6 in “Re: policy and mechanism for less-connected clients”
  1. Theodore TsoJun 25, 2008
  2. David JeskeJun 25, 2008
  3. Jakub NarebskiJun 25, 2008
  4. David JeskeAug 14, 2016
  5. Daniel BarkalowJun 25, 2008
  6. Raimund BauerJun 25, 2008

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.