From: Felipe Contreras <felipe.contreras@gmail.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Johannes Sixt <j6t@kdbg.org>,
Jonathan Nieder <jrnieder@gmail.com>,
"John J. Franey" <jjfraney@gmail.com>
Subject: Re: [PATCH] run-command: simplify wait_or_whine
Date: Sat, 1 Jun 2013 09:20:41 -0500 [thread overview]
Message-ID: <CAMP44s0uFLDanLP=w2ozVG665rCFq5kK7b5Mk_RWYEv39YqCqw@mail.gmail.com> (raw)
In-Reply-To: <CACsJy8D=oZ0Y0F8_WFfVxgFtnsRJtxxp9y2oQgoxpxd3zU+rsw@mail.gmail.com>
On Sat, Jun 1, 2013 at 9:08 AM, Duy Nguyen <pclouds@gmail.com> wrote:
> On Sat, Jun 1, 2013 at 9:06 PM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
>> On Sat, Jun 1, 2013 at 9:03 AM, Duy Nguyen <pclouds@gmail.com> wrote:
>>> On Sat, Jun 1, 2013 at 8:51 PM, Felipe Contreras
>>> <felipe.contreras@gmail.com> wrote:
>>>> Nobody is checking for specific error codes; it's the errno that's
>>>> important.
>>>
>>> Have you just disregarded the in-code comment you just removed with
>>> one statement?
>>
>> Who cares about the comment? As I said, nobody is checking for those codes.
>
> Apparently I do.
Why do you care about code comments that have no relation to reality?
>>> Did you check all its callers?
>>
>> Yes, that's why I said nobody is checking for those codes.
>
> Thanks. If would be a few mails less if you stated so in the original message.
So why did you think I said that that nobody is checking for those codes?
Anyway, apparently somebody added code that checks for the specific
code since I wrote this patch:
1250857 launch_editor: propagate signals from editor to git
To my knowledge this is the only place where the specific number us
actually checked.
--
Felipe Contreras
next prev parent reply other threads:[~2013-06-01 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 13:51 [PATCH] run-command: simplify wait_or_whine Felipe Contreras
2013-06-01 14:03 ` Duy Nguyen
2013-06-01 14:06 ` Felipe Contreras
2013-06-01 14:08 ` Duy Nguyen
2013-06-01 14:20 ` Felipe Contreras [this message]
2013-06-01 14:19 ` Thomas Rast
2013-06-01 14:23 ` Felipe Contreras
2013-06-01 14:21 ` Duy Nguyen
2013-06-01 14:30 ` Felipe Contreras
2013-06-01 14:36 ` Duy Nguyen
2013-06-01 15:01 ` Felipe Contreras
2013-06-01 17:24 ` [PATCH] t0005: test git exit code from signal death Jeff King
2013-06-01 21:41 ` Felipe Contreras
2013-06-01 17:01 ` [PATCH] run-command: simplify wait_or_whine Jeff King
2013-06-01 21:35 ` Felipe Contreras
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='CAMP44s0uFLDanLP=w2ozVG665rCFq5kK7b5Mk_RWYEv39YqCqw@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jjfraney@gmail.com \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.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).