public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Kjetil Barvik <barvik@broadpark•no>
To: Mike Ralphson <mike.ralphson@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH/RFC v1 5/6] combine-diff.c: remove a call to fstat()	inside show_patch_diff()
Date: Tue, 27 Jan 2009 13:03:49 +0100	[thread overview]
Message-ID: <86myddj6qi.fsf@broadpark.no> (raw)
In-Reply-To: <e2b179460901270135j6e4cb887radbe664ac98f39f1@mail.gmail.com>

Mike Ralphson <mike.ralphson@gmail•com> writes:

> 2009/1/26 Kjetil Barvik <barvik@broadpark•no>:
>> Currently inside show_patch_diff() we have and fstat() call after an
>> ok lstat() call.  Since we before the call to fstat() have already
>> test for the link case with S_ISLNK() the fstat() can be removed.
>
> s/have and/have an/ ?

  Correct! Will fix.  Thanks!

  -- kjetil

  reply	other threads:[~2009-01-27 12:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 21:17 [PATCH/RFC v1 0/6] git checkout: more cleanups, optimisation, less lstat() calls Kjetil Barvik
2009-01-26 21:17 ` [PATCH/RFC v1 1/6] symlinks.c: small cleanup and optimisation Kjetil Barvik
2009-01-28 20:36   ` ??? " Junio C Hamano
2009-01-29 14:19     ` Kjetil Barvik
2009-01-26 21:17 ` [PATCH/RFC v1 2/6] remove some memcpy() and strchr() calls inside create_directories() Kjetil Barvik
2009-01-28 20:36   ` Junio C Hamano
2009-01-26 21:17 ` [PATCH/RFC v1 3/6] cleanup of write_entry() in entry.c Kjetil Barvik
2009-01-28 21:31   ` Junio C Hamano
2009-01-26 21:17 ` [PATCH/RFC v1 4/6] use fstat() instead of lstat() when we have an opened file Kjetil Barvik
2009-01-26 21:17 ` [PATCH/RFC v1 5/6] combine-diff.c: remove a call to fstat() inside show_patch_diff() Kjetil Barvik
2009-01-27  9:35   ` Mike Ralphson
2009-01-27 12:03     ` Kjetil Barvik [this message]
2009-01-27 12:06       ` Mike Ralphson
2009-01-28 20:37   ` Junio C Hamano
2009-01-29  1:16     ` Junio C Hamano
2009-01-29  8:20       ` Kjetil Barvik

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=86myddj6qi.fsf@broadpark.no \
    --to=barvik@broadpark$(echo .)no \
    --cc=git@vger$(echo .)kernel.org \
    --cc=mike.ralphson@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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