From: Brian Koropoff <bkoropoff@gmail.com>
To: dash@vger.kernel.org
Subject: Portability patches
Date: Tue, 18 Jan 2011 21:07:16 -0800 [thread overview]
Message-ID: <1295413636.4278.28.camel@gemini> (raw)
Hi,
I've been working on a new build system (yeah, I know, *another* one)
that aims to be highly portable to various POSIX systems and light on
dependencies (in the spirit of autotools, though substantially less
insane). Pure POSIX sh turned out to be robust enough for my project,
but the various UNIX systems I've ported it to lack anything with dash's
raw speed. Naturally, I just ported dash to them as well.
Patch stack incoming. I expect some of these might need further
explanation or revision before being accepted.
Regards,
Brian Koropoff
next reply other threads:[~2011-01-19 5:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 5:07 Brian Koropoff [this message]
2011-01-19 5:15 ` [PATCH 1/3] Port to Solaris Brian Koropoff
2011-01-21 13:06 ` Jilles Tjoelker
2011-03-10 12:16 ` Herbert Xu
2011-03-13 1:18 ` Brian Koropoff
2011-03-13 1:25 ` [PATCH] " Brian Koropoff
2011-03-15 7:36 ` Herbert Xu
2011-01-19 5:15 ` [PATCH 2/3] Port to AIX Brian Koropoff
2011-03-10 12:25 ` Herbert Xu
2011-01-19 5:16 ` [PATCH 3/3] Port to HP-UX Brian Koropoff
2011-03-10 12:26 ` Herbert Xu
2011-03-12 23:54 ` Brian Koropoff
2011-03-15 7:38 ` Herbert Xu
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=1295413636.4278.28.camel@gemini \
--to=bkoropoff@gmail.com \
--cc=dash@vger.kernel.org \
/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