On Sat, 20 May 2006 19:05:31 -0400 Dave Jones <davej@xxxxxxxxxx> wrote: > 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 - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html