From: Alexandre Julliard <julliard@winehq.org>
To: git@vger.kernel.org
Subject: [PATCH 0/5] Shallow clone fixes
Date: Fri, 24 Nov 2006 15:57:15 +0100 [thread overview]
Message-ID: <8764d4vqno.fsf@wine.dyndns.org> (raw)
This series fixes a number of small problems in the shallow clone
support in pu. After that it seems to work fairly well for me.
The one remaining problem I see is that a git-fetch to deepen the tree
doesn't take into account the commits that the client already has. For
instance, on the Wine tree, a "git-clone --depth 1" downloads 4655
objects, and a "git-clone --depth 2" downloads 4660, so I'd expect
that after the depth 1 clone a "git-fetch --depth 2" would only have
to download 5 objects, but currently it downloads 4650 again.
--
Alexandre Julliard
next reply other threads:[~2006-11-24 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 14:57 Alexandre Julliard [this message]
2006-11-24 15:43 ` [PATCH 0/5] Shallow clone fixes Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8764d4vqno.fsf@wine.dyndns.org \
--to=julliard@winehq.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.