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

Re: dangling commits.

From
Sean <seanlkml@sympatico.ca>
Date
May 20, 2006, 23:08 UTC
Message-ID
<BAYC1-PASMTP12721518DAEC49D36EF4B8AEA40@CEZ.ICE>
In-Reply-To
<20060520230531.GA27511@redhat.com>

On Sat, 20 May 2006 19:05:31 -0400 Dave Jones <davej@redhat.com> wrote:

Show 16 quoted lines
> What's wrong here?
> 
> (tmp)$ mkdir git
> (tmp)$ cd git
> (git)$ rsync -azq rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/git.git/ .git
> (git)$ git-fsck-objects --full
> dangling commit fc024e5e1b92fb11d11aa3c15e9e3f92a888acb6
> dangling commit be49def3dd524b241e3f14c657e740f2e4d73d39
> dangling commit e659abda29b2b25db2771c3e6086f15bc74b1d06
> dangling commit 0f5aaf12d411debc2958dfb029ffcf873d980f15
> dangling commit 8eed8a5da8330df6901f254eab4b7056855b919c
> 
> The version of git on that box is 1.2.6-1 from Debian etch.
> 
> 		Dave
>

Nothing wrong. Those commits were just dropped from the "pu" branch at one time or another when it was rewound. The repository could use a pruning, but there's no harm done by having those objects remain in the object database. If you had used any protocol other than rsync, they would not have appeared in your cloned copy.

Sean
Previous: Dave JonesNext: Linus Torvalds
Message 2 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.