From: Junio C Hamano <gitster@pobox.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "András Kucsma via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Torsten Bögershausen" <tboegi@web.de>,
"András Kucsma" <r0maikx02b@gmail.com>
Subject: Re: [PATCH v3] run-command: trigger PATH lookup properly on Cygwin
Date: Fri, 27 Mar 2020 14:27:27 -0700 [thread overview]
Message-ID: <xmqqd08xfpz4.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <877dz5bpyd.fsf@igel.home> (Andreas Schwab's message of "Fri, 27 Mar 2020 19:41:30 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Mär 27 2020, Junio C Hamano wrote:
>
>> The name of the ASCII character '\0' is NUL, not NULL
>
> NUL is not a name, it is an abbreviation or acronym. Its name is the
> Null character.
OK, let's put it differently.
> + * See how long the non-separator part of the given path is, and
> + * if and only if it covers the whole path (i.e. path[len] is NULL),
When referring to character '\0' like so, write "NUL", not "NULL",
as the latter is how you write a null pointer.
prev parent reply other threads:[~2020-03-27 21:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 21:13 [PATCH] Fix dir sep handling of GIT_ASKPASS on Windows András Kucsma via GitGitGadget
2020-03-24 20:51 ` Junio C Hamano
2020-03-25 13:45 ` [PATCH v2] " András Kucsma via GitGitGadget
2020-03-25 16:35 ` Torsten Bögershausen
2020-03-25 17:09 ` András Kucsma
2020-03-26 21:16 ` Junio C Hamano
2020-03-26 21:14 ` Junio C Hamano
2020-03-27 0:21 ` András Kucsma
2020-03-27 0:36 ` [PATCH v3] run-command: trigger PATH lookup properly on Cygwin András Kucsma via GitGitGadget
2020-03-27 18:04 ` Junio C Hamano
2020-03-27 18:10 ` András Kucsma
2020-03-27 18:41 ` Andreas Schwab
2020-03-27 21:27 ` Junio C Hamano [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqd08xfpz4.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=r0maikx02b@gmail.com \
--cc=schwab@linux-m68k.org \
--cc=tboegi@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).