Re: [PATCH 5/6] Teach "fsck" not to follow subproject links

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Apr 12, 2007, 01:52 UTC
Message-ID: <Pine.LNX.4.64.0704111850240.4061@woody.linux-foundation.org>
In-Reply-To: <7vslb6mnva.fsf@assigned-by-dhcp.cox.net>

On Wed, 11 Apr 2007, Junio C Hamano wrote:

Show 5 quoted lines

>
> The small detail in the last step is wrong, though.  Even if
> they EXIST, they may be isolated commits that are note connected
> to refs, and fsck in the repository would not have warned about
> unreachable trees from such unconnected commits.

The superproject *is* a ref.

You cannot prune the subprojects on their own. That's the *only* real special rule about subprojects. Exactly because pruning them on their own is not a valid op to do.

It's the same way with an source of "alternate" objects (or a shared object directory) - you'd better not prune them, because other projects may have refs to them that you don't know about locally. So this isn't somethign new to subprojects.

		Linus