Hi, On Fri, 8 Jun 2007, Johan Herland wrote: > On Friday 08 June 2007, Johannes Schindelin wrote: > > > I just tried to fetch from one of my repos which was perfectly usable > > (and fetchable) before, and got this error message: > > > > error: char103: premature end of data > > Sorry about that. Do you have an idea of which tag object caused the > failure? If so, could you send the output of "git-cat-file tag <name>" > on it? Yes, I know what causes it. A tag with an empty message. And I even know why it does that. It's easy. Look into git-tag.sh, and you will find that it does a git-stripspace on the final message. If that was empty, then the tag will just be the tag header. > git-fsck on the repo should report the same error. If you run with -v > (verbose) you should also get some hints as to which tag object causes > this. Yes, it finds the error. And crashes. And costs me time. Why do we have to parse _everything_ in the tag to begin with? It's not like I will show the information of the darn thing when I just fetch it from repo A into repo B. Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
