From: "Issam E. Maghni" <issam.e.maghni@mailbox.org>
To: Junio C Hamano <gitster@pobox.com>,
Issam Maghni via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] hook: test -a|o is not POSIX
Date: Fri, 7 Jan 2022 17:31:18 -0500 (EST) [thread overview]
Message-ID: <1303411829.1252938.1641594678116@office.mailbox.org> (raw)
In-Reply-To: <xmqqr19j6x92.fsf@gitster.g>
> On 01/07/2022 4:39 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> "Issam Maghni via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
> > From: "Issam E. Maghni" <issam.e.maghni@mailbox.org>
> >
> > I faced `test: too many arguments` when building using sbase [1]
>
> Building "git" with sbase? It is curious how a loosely written
> sample hook script can cause build failures on a platform with a
> more strict userspace.
Sorry, I rather meant using git with sbase. I’ve submitted at least a
half dozen patches similar to this one. My brain is in auto-mode.
> Perhaps...
>
> The sample update script in the templates directory uses the
> `-o` and `-a` binary primaries of the "test" command, which
> are marked obsolescent in the recent versions of POSIX.
>
> ...would be sufficient, as 'sbase' would not be the only source of
> the userspace whose 'test' lack the -o/-a primaries.
You’re right, this is much cleaner.
I force-pushed the changes in https://github.com/git/git/pull/1172.
I must admit, I’m not familiar (yet) to submitting patches through
mailing lists.
next prev parent reply other threads:[~2022-01-07 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 4:03 [PATCH] hook: test -a|o is not POSIX Issam Maghni via GitGitGadget
2022-01-07 21:39 ` Junio C Hamano
2022-01-07 22:31 ` Issam E. Maghni [this message]
2022-01-09 8:14 ` Bagas Sanjaya
2022-01-09 18:32 ` 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=1303411829.1252938.1641594678116@office.mailbox.org \
--to=issam.e.maghni@mailbox.org \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--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).