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

Re: dangling commits.

From
Linus Torvalds <torvalds@osdl.org>
Date
May 20, 2006, 23:19 UTC
Message-ID
<Pine.LNX.4.64.0605201615270.3649@g5.osdl.org>
In-Reply-To
<20060520230531.GA27511@redhat.com>
On Sat, 20 May 2006, Dave Jones wrote:
>
> What's wrong here?
Nothing, except
 - you used rsync to fetch the thing (so you get all objects, regardless 
   of whether they are reachable or not)
 - junio re-bases his "pu" branch, and I just end up following him (I 
   should stop exporting git entirely, here's no point, really). Thus, 
   whenever "pu" gets reset to something else, the old head of pu gets 
   dropped on the floor and ends up as a "dangling" commit (no branch head 
   points to it any more).
The moral(s) of the story being that
 (a) dangling commits are normal if you reset branch heads (which includes 
     things like "git rebase", for example)
 (b) rsync is not a good transfer protocol, since it will just blindly 
     transfer objects that aren't needed - or worse - successfully clone a 
     corrupt repository.
but there's nothing to _worry_ about in this particular schenario.
		Linus
Previous: SeanNext: Dave Jones
Message 3 of 4 in “dangling commits.”
  1. Dave JonesMay 20, 2006
  2. SeanMay 20, 2006
  3. Linus TorvaldsMay 20, 2006
  4. Dave JonesMay 20, 2006

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.