git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Alex Riesen <raa.lkml@gmail.com>, Bill Lear <rael@zopyra.com>,
	git@vger.kernel.org
Subject: Re: git 1.5.3.5 error over NFS (pack data corruption)
Date: Tue, 13 Nov 2007 17:32:06 -0800	[thread overview]
Message-ID: <7vfxz9pq7d.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711132027430.21255@xanadu.home> (Nicolas Pitre's message of "Tue, 13 Nov 2007 20:28:59 -0500 (EST)")

Nicolas Pitre <nico@cam.org> writes:

> On Wed, 14 Nov 2007, Alex Riesen wrote:
> ...
>> 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 "...
>
> This is not included in 1.5.3.5 though.

True; although I did not think it was risky at all, I did not
think that was serious enough change.

  reply	other threads:[~2007-11-14  1:32 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
2007-11-14  1:28               ` Nicolas Pitre
2007-11-14  1:32                 ` Junio C Hamano [this message]
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=7vfxz9pq7d.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=raa.lkml@gmail.com \
    --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).