Re: [RFC] shallow clone
- From
Junio C Hamano <junkio@cox.net>
- Date
- Jan 31, 2006, 08:51 UTC
- Message-ID
- <7vvew03hls.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <cda58cb80601310037s58989b26s@mail.gmail.com>
Franck <vagabon.xyz@gmail.com> writes:
> 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...
Mind writing up a howto on the topic?
- How things are set up using the current tool. - How others initially clone from you. - How others update (pull) from you. - What are the pitfalls you and others need to avoid (i.e. operations that involve old history)
I brought this up, because lack of official support of shallow cloning was cited as one of the showstopper for a project that once considered switching to git but didn't, from a mailing list research.