Shallow clone support

[dougrathbone]

Hi there

I was hoping for support for git clone --depth 1 so that we can support init'ing repos without all the history data.

I'd be happy to have a go but am totally new to the project (as in, 5 mins new)

[ben]

Absolutely, have a go! You might want to see how core git does this, it's probably something in the request sent to the remote. Then take a look at src/fetch.c, the changes will probably start there. Good luck, and don't be afraid to ask questions; we hang out in #libgit2 on irc.freenode.net.

[dougrathbone]

i'm taking a look at this now. Seeing i've never written in c, i'm a bit out of the loop on how to use interop or even what I am meant to be looking for.

what i've done to date:

• i've started to add a unit test for CanCloneShallow
• i've added an optional parameter to Repository.cs
• started digging around the clone support in libgit2 (dont think there is any depth at all.
• felt a bit lost as I am not a c programmer at_all

some updates on how JGit have been looking at it over the years:

• http://dev.eclipse.org/mhonarc/lists/jgit-dev/msg00512.html

[dunmatt]

nudge nudge

I'm looking at libgit for a project I have on the drawing board, but it would need this feature. I do know C, but I don't know either the libgit codebase or the git codebase. Does anyone here have an intuition as to how much work adding this feature would be?

[nulltoken]

I do know C, but I don't know either the libgit codebase or the git codebase.

Hey, that's great! We would be very pleased to help you work on this.

Does anyone here have an intuition as to how much work adding this feature would be?

/cc @carlosmn @ethomson Thoughts?

[ethomson]

I think discussing it over in a libgit2 issue would be great. We've been thinking about working on this as well, it would be great to pair up.

-ed

On Nov 13, 2014, at 2:46 PM, nulltoken notifications@github.com wrote:

I do know C, but I don't know either the libgit codebase or the git codebase.

Hey, that's great! We would be very pleased to help you work on this.

Does anyone here have an intuition as to how much work adding this feature would be?

/cc @carlosmn @ethomson Thoughts?

—
Reply to this email directly or view it on GitHub.

[AmadeusW]

I'm also interested in working on shallow copies.
For reference, here's a closed discussion on libgit2 and unfortunately not too many search results for 'shallow clone'

[burdges]

Appears the recent discussion is here : libgit2/libgit2#3058

[litetex]

This issue is now nearly 8 years old.
The corresponding issue at libgit2/libgit2#3058 is 5 years old.

Will this get implemented soon?
Is there any new information?
(libgit2 has a open PR, but there is currently no progress / was forgotten?; however when it is implemented in libgit2, it must still get implemented here to make it finally working, but I have no idea how long that would take)

In my use-case I just want to use git fetch --prune --unshallow but with the API 😄

[tschissler]

Any progress on this issue?