Re: [QUESTION] about .git/info/grafts file
- From
Andreas Ericsson <ae@op5.se>
- Date
- Jan 19, 2006, 11:10 UTC
- Message-ID
- <43CF739F.2030204@op5.se>
- In-Reply-To
- <7v8xtdrqwg.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
Show 16 quoted lines
> Franck <vagabon.xyz@gmail.com> writes: > > >>I'm wondering why the "grafts" files is not involved during >>push/pull/clone operations ? > > > Commit ancestry grafting is a local repository issue and even if > you manage to lie to your local git that 300,000th commit is the > epoch, the commit object you send out to the downloader would > record its true parent (or parents, if it is a merge), so the > downloader would want to go further back. And no, rewriting > that commit and feeding a parentless commit to the downloader is > not an option, because such a commit object would have different > object name and unpack-objects would be unhappy. >
I'm a bit curious about how this was done for the public kernel repo. I'd like to import glibc to git, but keeping history since 1972 seems a bloody waste, really.
-- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231