Re: SCSI trees, merges and git status

From: David Woodhouse <dwmw2@infradead.org>
Date: Apr 19, 2005, 00:41 UTC
Message-ID: <1113871307.3579.21.camel@localhost.localdomain>
In-Reply-To: <1113869817.4998.106.camel@mulgrave>

On Mon, 2005-04-18 at 19:16 -0500, James Bottomley wrote:

Show 5 quoted lines

> Yes, that's what I did to get back to the commit just before the
> merge:
> 
> fsck-cache --unreachable 54ff646c589dcc35182d01c5b557806759301aa3|awk
> '/^unreachable /{print $2}'|sed 's:^\(..\):.git/objects/\1/:'|xargs rm

I was actually digressing and talking about pruning ancient history which _is_ theoretically reachable. It's not being 'undone'; it's just being omitted from the current _working_ tree. The whole point is that in a fully-populated tree the history _should_ be accessible all the way back.

We're trying to get the older history available on kernel.org ASAP. The blobs are rsyncing to ~dwmw2/git/kernel-tglx1; the trees and commit objects will be coming soon.

Theoretically all Linus actually needs in order to rebuild his current tree is the sha1 hash of the final commit in that historical tree, which corresponds to 2.6.12-rc2.

-- 
dwmw2