On 10/20/05, Junio C Hamano <junkio@cox.net> wrote: > Martin Langhoff <martin.langhoff@gmail.com> writes: > > >> GIT_DIR=../.. git-rev-parse --verify "$tagid^0" >/dev/null 2>&1 && continue > > > > Note however that git-rev-parse is lazy and won't check that the > > commit is there. I have to call git-cat-file and check whether it > > succeeds to know if we have the object. > > Are you sure? > > What "rev^0" does is: Ok -- I was using ^{commit} which _is_ lazy, but you are right, ^0 isn't lazy. > BTW, I just got a SEGV while pulling Cogito repository over > git-fetch-pack after interrupting rsync transfer (I wanted to > switch to git transfer). I am running with Johaness patch from > today so the cause may be different from yours, but now I have > something to look at, which is better than before. > > Fetching with rsync (and interrupting in the middle) is a good > way to simulate a broken repository ;-). Cool. That's something for you to play with I guess, to tell you the truth, I'm not useful with gdb ;) martin - 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.htmlReceived on Thu Oct 20 15:00:34 2005
This archive was generated by hypermail 2.1.8 : 2005-10-20 15:00:37 EST