Re: how to filter a pull

From: marc zonzon <marc.zonzon@gmail.com>
Date: May 4, 2007, 13:13 UTC
Message-ID: <71295b5a0705040613m74215667w72db82e0bc2c1a58@mail.gmail.com>
In-Reply-To: <20070504101329.GA16446@diana.vm.bytemark.co.uk>

On 5/4/07, Karl Hasselström <kha@treskal.com> wrote:

Show 7 quoted lines

> It should be straightforward (and efficient) to make a script that
> takes an existing branch and makes a parallel branch that contains
> only one subtree of the first branch. This derived branch can then be
> used as a subproject or whatever.
>
> Or is there some obvious reason why this wouldn't work, or would be
> inconvenient?

This was my initial idea, pull and filter!, but of course it is somewhat a hack, you pull inside git, and filter outside git, I don't know how to keep history, it seems that once filtered the origin of the subtree is lost. But I lack of git proficiency, I have no experience wich git core and mainly have used it at the user 'porcelain' level. I have had some hope that there is some mean to forward the internal state recording of the database state. The solution proposed by alex does not seem to be an option, if you draw from many projects, you cannot host the whole trees because some nodes are duplicates, and if they are outside your field you don't bother of merging them. Moreover I don't know how you mark what belongs to your small project island, among this big ocean.

So if I have no further advice I think the wiser is to try the raw script option, at least for the next 6 months the time to git, and my own proficiency to ripen..

Marc