From: Josef Weidendorfer Date: Sun, 17 Dec 2006 23:38:34 GMT Subject: Re: What's cooking in git.git (topics) Message-ID: <200612180038.34525.Josef.Weidendorfer@gmx.de> In-Reply-To: <20061217173534.GA16838@nan92-1-81-57-214-146.fbx.proxad.net> On Sunday 17 December 2006 18:35, Yann Dirson wrote: > An idea I had to handle that case, and which could be useful with the > current problem, as well as others, like dealing with stgit's patch > logging, would be to define "reachable commits" using a modular > architecture. That way we would be able to select what we want > fsck-object/prune to consider reachable, in objects reachable from: > > - raw "parents" field of commit objects > - the latter as modified by info/grafts > - reflogs > - stgit patchlogs Could be interesting for pruning support in submodules, too. > The set of rules to consider could be declared in repo-config, thus > stgit would be able to declare that its patchlogs should not be ignored, > and people wishing to prune commits hidden by grafts in one repo could > just remove the "raw-parents" rule from their repo's config. > > Obviously, mentionning stgit-specific rules here immediately suggests a > plugin-based architecture. Isn't it enough to specify further subdirectories of .git/, holding references which should be taken into account while pruning? Hmm.. Grafting would be a special case.