Hi, On Wed, May 02, 2007 at 06:27:51PM CEST, Jan Holesovsky wrote: > On Wednesday 02 May 2007 18:15, Petr Baudis wrote: > > > On Wed, May 02, 2007 at 04:24:24PM CEST, Jan Holesovsky wrote: > > > > What might help here is splitting repository into current (e.g. from > > > > OOo 2.0) and historical part, > > > > > > No, I don't want this ;-) > > > > Are you sure? Using the graft mechanism, Git can make this very easy and > > almost transparent for the user - when he clones he gets no history but > > he can use say some simple vendor-provided script to download the > > historical packfile and graft it to the 'current' tree. After that, the > > graft acts completely transparently and it 'seems' like the history > > goes on continuously from OOo prehistory up to the latest commit. > > Interesting, I did not know that it is possible to do it so that it appears > transparently; this would be indeed a tremendous win - we could start nearly > from scratch ;-) > > Please - where could I find more info? Like what does the script have to do, > etc. you can see an example script at http://repo.or.cz/w/elinks.git?a=blob;f=contrib/grafthistory.sh and I have tried vainly few times to get a similar script to the kernel too http://lists.zerezo.com/linux-kernel/msg6599002.html that can use both wget and curl and will also download tag refs for the history. The format of the grafts file itself (.git/info/grafts) is pretty simple (just one-graft-per-line where you first say the commit id and then the parent commit(s) to be drafted onto it), please see Documentation/repository-layout.txt for details. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ Ever try. Ever fail. No matter. // Try again. Fail again. Fail better. -- Samuel Beckett - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html