From: Alex Riesen <raa.lkml@gmail.com>
To: Bill Lear <rael@zopyra.com>
Cc: git@vger.kernel.org
Subject: Re: git 1.5.3.5 error over NFS (pack data corruption)
Date: Wed, 14 Nov 2007 20:54:06 +0100 [thread overview]
Message-ID: <20071114195406.GB3973@steel.home> (raw)
In-Reply-To: <18234.15666.711624.443184@lisa.zopyra.com>
Bill Lear, Wed, Nov 14, 2007 01:11:30 +0100:
> >oh, you should be looking for usage.c, the function report (it is
> >called by default die handler). The old code used to fputs("fatal:"),
> >the new just vfprintf's everything, so the write should look like:
> >
> > write(2, "fatal: cannot pread pack file: No such "...
>
> Are you sure?
>
> % ls -l git-1.5.3.5.tar.bz2
> -rw-r--r-- 1 blear software 1351433 2007-10-31 15:04 git-1.5.3.5.tar.bz2
> % bunzip2 -c !$ | tar xf -
> % cd git-1.5.3.5
> % grep -A 5 'void report' usage.c
> static void report(const char *prefix, const char *err, va_list params)
> {
> fputs(prefix, stderr);
> vfprintf(stderr, err, params);
> fputs("\n", stderr);
Ach, right. I just checked Junio's master. BTW, maybe you could check
that as well? There were 64bit fixes lately, and had an impression you
were using git compiled for 64bit (mmap2 return address from your
first strace was shown 64bit).
next prev parent reply other threads:[~2007-11-14 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 15:31 git 1.5.3.5 error over NFS Bill Lear
2007-11-09 23:21 ` Alex Riesen
2007-11-12 15:39 ` Bill Lear
2007-11-12 23:31 ` Alex Riesen
2007-11-12 23:33 ` Alex Riesen
2007-11-13 14:49 ` Bill Lear
2007-11-13 21:48 ` git 1.5.3.5 error over NFS (pack data corruption) Alex Riesen
2007-11-13 23:56 ` Bill Lear
2007-11-14 0:02 ` Alex Riesen
2007-11-14 0:11 ` Bill Lear
2007-11-14 19:54 ` Alex Riesen [this message]
2007-11-14 1:28 ` Nicolas Pitre
2007-11-14 1:32 ` Junio C Hamano
2007-11-14 1:38 ` git 1.5.3.5 error over NFS Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071114195406.GB3973@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=rael@zopyra.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).