Re: [PATCH] clone,fetch: explain the shallow-clone option a little more clearly

On Wed, Dec 7, 2016 at 1:29 AM, Junio C Hamano wrote: > Duy Nguyen writes: > >> On Tue, Dec 6, 2016 at 1:28 AM, Junio C Hamano wrote: >>> I however offhand do not think the feature can be used to make the >>> repository shallower >> >>

Re: [PATCH] clone,fetch: explain the shallow-clone option a little more clearly

Duy Nguyen writes: > On Tue, Dec 6, 2016 at 1:28 AM, Junio C Hamano wrote: >> I however offhand do not think the feature can be used to make the >> repository shallower > > I'm pretty sure it can,... I wrote my message after a short local testing, but it

Re: [PATCH] clone,fetch: explain the shallow-clone option a little more clearly

On Tue, Dec 6, 2016 at 1:28 AM, Junio C Hamano wrote: > I however offhand do not think the feature can be used to make the > repository shallower I'm pretty sure it can, though it's a waste because you should be able to shorten your history without talking to a remote server.

Re: [PATCH] clone,fetch: explain the shallow-clone option a little more clearly

Alex Henrie writes: > "deepen by excluding" does not make sense because excluding a revision > does not deepen a repository; it makes the repository more shallow. I think that an intuitive way the feature should work may be: - You started with "git fetch --depth=20"

[PATCH] clone,fetch: explain the shallow-clone option a little more clearly

"deepen by excluding" does not make sense because excluding a revision does not deepen a repository; it makes the repository more shallow. Signed-off-by: Alex Henrie --- builtin/clone.c | 2 +- builtin/fetch.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)