Dirk Behme <[EMAIL PROTECTED]> writes:
>>>Seems to me that this breaks http update
Let's clarify one thing first. Did you mean "git rebuilt from
the sources obtained from that seemingly-odd commit, http update
does not work anymore", or did you mean "starting from the state
my repository happened to be in, attempting to pull from the
git.git repository did not work, and the master branch head of
git.git public repository was that commit"?
First we need to make sure your git binary from last week
wednesday or thursday is recent enough. I think you need at
least this commit:
Author: Daniel Barkalow <[EMAIL PROTECTED]>
Date: Thu Aug 11 23:17:55 2005 -0400
[PATCH] Also parse objects we already have
In the case where we don't know from context what type
an object is, but we don't have to fetch it, we need to
parse it to determine the type before processing it.
If your git binary turns out to be recent enough, then the state
of your repository is needed to diagnose this problem. What do
these command tell you in your git.git repository that cg-pull
from the public repository fails?
$ git fsck-cache | grep -v '^dangling '
$ git ls-remote --heads ./.
$ ls .git/objects/pack
[Note to people who are interested in what I plan to do with the
output from the above commands. If fsck-cache reports any
anomaly other than dangling objects, that means the repository
before pulling is corrupt and the problem is not in http-pull.
Otherwise, I can first make a clone of my git.git repository
while expanding all the packs, overwrite the head references to
what "git ls-remotes" reports for Dirk's repository, run "git
prune" to lose objects Dirk would not have, and then try
running git-http-pull myself.
What set of packs Dirk has (and does not have) is there for
sanity checking --- if he has packs that I do not have myself,
that means he packed his repository himself. Which is not an
illegal thing to do at all, and I do not think that would
affect the operation of http-pull, it would be a good thing to
know while digging deeper, hence the request for that
information. ]
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
