git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Eric Wong <e@80x24.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2016, #03; Fri, 8)
Date: Sun, 10 Jul 2016 00:45:29 -0400	[thread overview]
Message-ID: <20160710044529.GA10777@sigill.intra.peff.net> (raw)
In-Reply-To: <20160710034736.GA19151@dcvr.yhbt.net>

On Sun, Jul 10, 2016 at 03:47:36AM +0000, Eric Wong wrote:

> > There was one minor improvement I suggested[1] (and which you seemed to
> > like), which is to push the errno check into the function. That wasn't
> > expressed in patch form, though, so I've included below a version of
> > your patch with my suggestion squashed in.
> 
> Yes, I'm fine with either, but I'm slightly thrown off by
> a function relying on errno being set by the caller, even if it
> is errno.  So maybe localizing it is better (see below)

Yeah, I had a similar reservation, but didn't want to clutter the
interface. However, just passing errno isn't too bad (as you showed
below), and is much less magical.

Do you want to squash that and re-send the whole patch to make Junio's
life easier?

> > Since both conditionals just call "continue", you could actually fold
> > them into a single if() in each caller, but I think it's easier to
> > follow as two separate ones.
> > 
> > You could actually fold the t
> 
> Copy-paste error?

Nope, just typing error while revising. :)

-Peff

  reply	other threads:[~2016-07-10  4:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 22:59 What's cooking in git.git (Jul 2016, #03; Fri, 8) Junio C Hamano
2016-07-09 23:25 ` Eric Wong
2016-07-11 17:51   ` Junio C Hamano
2016-07-09 23:45 ` Eric Wong
2016-07-10  2:52   ` Jeff King
2016-07-10  3:47     ` Eric Wong
2016-07-10  4:45       ` Jeff King [this message]
2016-07-10  8:20         ` [PATCH 3/2] hoist out handle_nonblock function for xread and xwrite Eric Wong
2016-07-11  6:24 ` What's cooking in git.git (Jul 2016, #03; Fri, 8) Johannes Schindelin
2016-07-11 17:13   ` Junio C Hamano

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=20160710044529.GA10777@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).