Thanks. This is very puzzling.
This part looks quite sane.
$ git rev-list --objects ^7cf712d v2.6.25-rc1^0 | wc -l
328
and the number of received objects exactly match.
This is however very unexpected. The sequence internally should
be doing the equivalent of:
- fetch the objects to complete the branches we track
(i.e. what the above "rev-list" that fetches to complete the
commit pointed by the v2.6.25-rc1 tag based on your earlier
tip 7cf712d);
- store the tip (19af355 = v2.6.25-rc1^0) to the tracking
branch;
- run another "git fetch" to retrieve objects to complete the
v2.6.25-rc1 tag itself, based on our available refs (which
includes the commit 19af355).
which should result in transferring only one object, which would
say something like:
From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
7cf712d..19af355 master -> linus
remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (1/1), done.
From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
* [new tag] v2.6.25-rc1 -> v2.6.25-rc1
Updating 7cf712d..19af355
We would need a bit more digging to reproduce it, as I do not
seem to be able to.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
