From: joshuakraemer <joshuakraemer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dosbox: patch to support full mapping of joysticks
Date: Sat, 09 May 2020 13:44:28 +0200 [thread overview]
Message-ID: <20200509114428.nFH0QXLwrQ0J6JHKwyzoEq0D1ALZGZ1YLQGEE5z_QzU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14474@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
New comment by joshuakraemer on void-packages repository
https://github.com/void-linux/void-packages/pull/14474#issuecomment-626153548
Comment:
Thank you @ericonr and @abenson, I did not know about dosbox-staging. I have already thought about packaging dosbox-ece (template here: https://github.com/joshuakraemer/void-packages/commit/c926d794e8e5dffb2e96aee274f6d3253da29222), but I think dosbox-staging is the better choice. I would second packaging it.
While it does not solve the original issue (full mapping of controllers), the team seems to be more open to community suggestions, so I will file an issue with them.
Edit: dosbox-staging issue: https://github.com/dosbox-staging/dosbox-staging/issues/342
next prev parent reply other threads:[~2020-05-09 11:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 18:41 [PR PATCH] " voidlinux-github
2019-09-15 19:02 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-15 19:02 ` voidlinux-github
2019-09-16 14:30 ` voidlinux-github
2019-09-20 20:11 ` voidlinux-github
2020-05-02 14:15 ` [PR PATCH] [Updated] " joshuakraemer
2020-05-06 19:30 ` ericonr
2020-05-07 2:05 ` abenson
2020-05-07 9:55 ` pullmoll
2020-05-07 10:49 ` abenson
2020-05-07 11:25 ` pullmoll
2020-05-09 11:27 ` joshuakraemer
2020-05-09 11:44 ` joshuakraemer [this message]
2021-07-16 15:29 ` ericonr
2021-07-16 15:29 ` [PR PATCH] [Closed]: " ericonr
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=20200509114428.nFH0QXLwrQ0J6JHKwyzoEq0D1ALZGZ1YLQGEE5z_QzU@z \
--to=joshuakraemer@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).