Re: [RFC] shallow clone

From: Franck <vagabon.xyz@gmail.com>
Date: Jan 31, 2006, 11:11 UTC
Message-ID: <cda58cb80601310311v45531fb5u@mail.gmail.com>
In-Reply-To: <7vvew03hls.fsf@assigned-by-dhcp.cox.net>

2006/1/31, Junio C Hamano <junkio@cox.net>:

Show 8 quoted lines

> 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?

ok I'll try to sum-up something this week, hope my bad english will be understandable...

Show 6 quoted lines

>
>  - 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)

actually I just discovered one thanks to your first email for this thread about reverted commit...So I'm not very the one for this section...

Show 5 quoted lines

>
> 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.

again I wasn't aware that this feature is really needed...

thanks
--
               Franck