Re: [RFC] shallow clone
- From
- Franck <vagabon.xyz@gmail.com>
- Date
- Jan 31, 2006, 08:37 UTC
- Message-ID
- <cda58cb80601310037s58989b26s@mail.gmail.com>
- In-Reply-To
- <7v64o18qn4.fsf@assigned-by-dhcp.cox.net>
2006/1/30, Junio C Hamano <junkio@cox.net>:
Show 11 quoted lines
> Simon Richter <Simon.Richter@hogyros.de> writes: > > >> - disallow fetching from this repo, and > > > > Why? It's perfectly acceptable to pull from an incomplete repo, as > > long as you don't care about the old history. > > I agree. As long as the cloned one can record itself as a > shallow one (and with what epochs), I do not see a reason to > forbid second generation clone from a shallow repository. >
I agree too
Show 6 quoted lines
> Cauterizing is not any more special than other grafts entries. > If you have grafted historical kernel repository behind the > official kernel repository with 2.6.12-rc2 epoch, I do not think > of any reason to forbid people from cloning such with the > grafts. >
I built my public repository from a cautorized one and everybody who is pulling from mine is aware of the lack of the full history but they actually don't care. If someone is pulling from my repo, he actually wants to work on my project which do not need any old thing...
Thanks
--
Franck