From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Max Kirillov <max@max630.net>,
git@vger.kernel.org, Karthik Nayak <karthik.188@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
Michael Haggerty <mhagger@alum.mit.edu>
Subject: Re: [PATCH] strtoul_ui: actually report error in case of negative input
Date: Tue, 15 Sep 2015 18:17:03 -0700 [thread overview]
Message-ID: <xmqqsi6ftb74.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <vpq4miwfa78.fsf@anie.imag.fr> (Matthieu Moy's message of "Tue, 15 Sep 2015 08:50:03 +0200")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> Not just the return type (which is the error status), but also the type
> of the result argument indeed. It's not clear to me whether this is
> intentional (09f2825 (git-grep: don't use sscanf, 2007-03-12) introduced
> it, the commit message doesn't help). I first read strtoul_ui as
> "strtoul with a better UI (user interface)", but maybe the name was
> meant to say "a fuction that uses strtoul and returns an ui (unsigned
> int)".
Just for this part. Yes, ui does not mean user interface but "we
are grabbing an unsigned int and as its internal implementation we
happen to use strtoul" is where the name comes from.
> I went through the thread quickly, my understanding is that there were
> more work to do, but no objection to merging.
Yes, there were some in-flight topics that interfered with it and
the topic quickly went stale without getting rerolled. There wasn't
any fundamental issue with the topic itself.
next prev parent reply other threads:[~2015-09-16 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 22:00 [PATCH] strtoul_ui: actually report error in case of negative input Max Kirillov
2015-09-14 6:30 ` Matthieu Moy
2015-09-14 20:26 ` Max Kirillov
2015-09-15 6:50 ` Matthieu Moy
2015-09-16 1:17 ` Junio C Hamano [this message]
2015-09-16 4:20 ` Max Kirillov
2015-09-16 6:08 ` Matthieu Moy
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=xmqqsi6ftb74.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=max@max630.net \
--cc=mhagger@alum.mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.