On Thu, 22 Sep 2005, Daniel Barkalow wrote: > > > > It's not entirely trivial. The biggest bummer is that we'd have to fake > > out the parent info (ie the "parent" would have to be the previous entry > > that changes it, not the real one). > > How about a program that made the fake thing real? That is, actually wrote > to the database the entire history with only those paths included, and > only commits that change those paths. I think it would be a fine thing to do. If/once git-rev-list can do the "limit by filename" part, generating a new git history that uses that shouldn't be that hard. And yes, it would be a way to generate a "subproject" automatically. Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Sep 23 07:27:37 2005
This archive was generated by hypermail 2.1.8 : 2005-09-23 07:27:40 EST