Re: Problem cloning the Linux history tree

Wolfgang Denk [off-list ref] writes:

Missing object of tag v2.6.14-rc3... unable to retrieve

I do not have a clue on this one; I am assuming that it is
coming from cg-fetch.

[Fri Nov 04 09:55:13 2005] [error] [client 84.150.96.170] File does not exist: /srv/git/linux-2.6-denx.git/objects/bc

These directories really don't exist:

$ cd /srv/git/linux-2.6-denx.git/objects
. ls -l
total 8
drwxrwxr-x  2 wd wd 4096 Nov  4 09:52 info
drwxrwxr-x  2 wd wd 4096 Nov  3 15:15 pack

Quick question.  Is the source repository fully packed (i.e. git
repack followed by git prune)?  If that is the case there is
nothing to worry about.  The latest git prunes empty
$GIT_OBJECT_DIRECTORY/??/ directories and recreates them on
demand.

The question is : why are they requested?

Fetching over http is what we call a "commit walker" -- it
learns the top commit object names, gets that object and reads
it to learn what other objects it needs to slurp, and keeps
asking the next object, one by one.  When dealing with a packed
repository, it first asks individual objects (expecting they
would be found in $GIT_OBJECT_DIRECTORY/??/ directory), and when
not found it fetchs packs and looks inside.  Recent commit
walker knows how to issue multiple requests while earlier
request is still in transit, so you can expect some requests to
individual objects.  That is benign.

quoted

Cloning over git native transport should work, though:

    $ git clone git://git.kernel.org/pub/scm/lin.../history.git history

This does not work for me,  either.

The above uses git:// URL  but your failure below uses http://

-> git clone http://www.denx.de/git/linux-2.6-denx.git bar
...
walk c264852726dde251a0c09ec22f61a9be8b0db68b
walk 69903d6500c73af8329a5fba7153b0d50748981c
walk b59a9504cb93db7fae31e60760725d48652a1fc3
error: Could not interpret tags/DENX-2005-10-02-18:30 as something to pull

This one I can answer.  It is the colon in your tag name.
Please rename it to make git-check-ref-format(1) happy, run
git-update-server-info(1) and try again.