git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Habouzit <madcoder@artemis.madism.org>
To: Jim Meyering <jim@meyering.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git list <git@vger.kernel.org>
Subject: Re: [PATCH] bundle, fast-import: detect write failure
Date: Thu, 10 Jan 2008 19:18:38 +0100	[thread overview]
Message-ID: <20080110181838.GC27808@artemis.madism.org> (raw)
In-Reply-To: <87lk6xftdn.fsf@rho.meyering.net>

[-- Attachment #1: Type: text/plain, Size: 653 bytes --]

On Thu, Jan 10, 2008 at 06:05:56PM +0000, Jim Meyering wrote:
> Pierre Habouzit <madcoder@artemis.madism.org> wrote:
> ....
> >> On the other hand, if that write failure is truly ignorable,
> >> a mindless minimalist :-) might argue that it's best just to
> >> omit the syscall.
> >
> >   And leak a file descriptor :)
> 
> Not that mindless.
> The *write* syscall, not the close.
> I would never suggest eliminating the close.

  oh *oops*
> -
> 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.html

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-01-10 18:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10  8:54 [PATCH] bundle, fast-import: detect write failure Jim Meyering
2008-01-10  9:17 ` Pierre Habouzit
2008-01-10 12:05 ` Johannes Schindelin
2008-01-10 12:26   ` Jim Meyering
2008-01-10 12:37     ` Johannes Schindelin
2008-01-10 13:00       ` Jim Meyering
2008-01-10 16:25         ` Pierre Habouzit
2008-01-10 18:05           ` Jim Meyering
2008-01-10 18:18             ` Pierre Habouzit [this message]
2008-01-11  9:14           ` Jakub Narebski
2008-01-11  7:36         ` Junio C Hamano
2008-01-11  9:37           ` David Tweed
2008-01-11 11:39           ` Johannes Schindelin

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=20080110181838.GC27808@artemis.madism.org \
    --to=madcoder@artemis.madism.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jim@meyering.net \
    /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).