Re: [PATCH] Teach filter-branch about subdirectory filtering

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jun 8, 2007, 13:03 UTC
Message-ID: <Pine.LNX.4.64.0706081358060.4059@racer.site>
In-Reply-To: <46690315.8244CAF7@eudaptics.com>

Hi,

On Fri, 8 Jun 2007, Johannes Sixt wrote:

Show 14 quoted lines

> Johannes Schindelin wrote:
> > It's just a guess, but now that we come really, really close to having 
> > a concise implementation of git-subproject which will probably soon 
> > propagate to master, and then maint, I gather that more and more 
> > people come and want to split their projects (which they maintained as 
> > one big project) into several subprojects (which they should have been 
> > from the start, but the tool did not easily allow for that).
> 
> I think that --subdirectry-filter needs to become a bit smarter to be 
> really useful for splitting a big project into sub-projects plus a 
> super-project. The reason is that once you have extracted the 
> sub-project(s), you have a hard time to find out which commits to 
> gitlink into the super-project. I don't have a plan how to make it 
> smarter, though.

Yes, it seems a good direction to follow.

I will have to think about it, but I guess that with yet another set of files in ../map/ (probably prefixed by the subdirectory name), we should even be able to smartly filter a huge project into a super-project together with its subprojects.

The command line option would be something like "--split-superproject dir1,dir2,dir3", where dir<n> are the subdirectories that are to become the subprojects.

Ciao, Dscho