Johannes Zellner 6f3448191b Submit upstream contributions (2 PRs + 1 issue) 1 bulan lalu
..
01-uunicorn-wine-modern-toolchain.md 8b23cb756d Add upstream contribution drafts; generalize sandbox patch 1 bulan lalu
02-uunicorn-sandbox-argv-dispatch.md 8b23cb756d Add upstream contribution drafts; generalize sandbox patch 1 bulan lalu
03-rstar000-synaTudor-progress.md 8b23cb756d Add upstream contribution drafts; generalize sandbox patch 1 bulan lalu
README.md 6f3448191b Submit upstream contributions (2 PRs + 1 issue) 1 bulan lalu

README.md

Upstream contribution drafts

Ready-to-paste GitHub drafts for giving something back to the projects this setup builds on. Each .md file contains the title and body; the patch to attach lives in ../patches/.

Draft Target Patch to attach
01-uunicorn-wine-modern-toolchain.md uunicorn/wine branch hacking/validiy-sensor ../patches/uunicorn-wine-modern-toolchain.patch
02-uunicorn-sandbox-argv-dispatch.md uunicorn/synaWudfBioUsb-sandbox ../patches/uunicorn-sandbox-argv-dispatch.patch
03-rstar000-synaTudor-progress.md rstar000/synaTudor (upstream: Popax21/synaTudor) ../patches/synaTudor-work.patch

Submitted (2026-10-13)

Draft Submission
01 https://github.com/uunicorn/wine/pull/3 — base hacking/validiy-sensor
02 https://github.com/uunicorn/synaWudfBioUsb-sandbox/pull/8
03 https://github.com/Popax21/synaTudor/issues/69 — rstar000/synaTudor has issues disabled, so posted upstream; the 67KB patch is split across the issue and one follow-up comment

Posted from the nebulade forks via the prepared branches below.

How to submit

PRs (01, 02) — GitHub's web UI can't attach arbitrary .patch files to a PR; the clean way is:

  1. Fork the target repo; clone your fork.
  2. Apply the patch and commit(s):

    git checkout -b fix/modern-toolchain   # or: feature/argv-dispatch
    git apply /home/nebulon/projects/fingerprint/work/patches/<patch>
    git add -A && git commit -m "<short message>"
    git push -u origin fix/modern-toolchain
    

    (For 01-uunicorn-wine, open the PR against the hacking/validiy-sensor branch of uunicorn/wine.)

  3. Paste the draft title/body into the PR form. The patch text is also handy as a fallback for an issue ("patch attached below" + paste the diff).

Issue (03) — create the issue in rstar000/synaTudor and drag & drop ../patches/synaTudor-work.patch into the description box (GitHub issues accept file attachments).

Prepared branches (2026-10-13)

Both PR branches are committed locally with the patches applied, and exported as small git bundles (verified fetchable):

Target Branch Base Bundle
uunicorn/wine modern-toolchain-build-fixes (clone: /tmp/opencode/wine-validity) hacking/validiy-sensor @ 7a69a82 ../patches/uunicorn-wine-modern-toolchain.bundle
uunicorn/synaWudfBioUsb-sandbox argv-dispatch (clone: work/synaWudfBioUsb-sandbox) master @ f7b31df ../patches/uunicorn-sandbox-argv-dispatch.bundle

The wine clone lives in /tmp (volatile) — if it is gone, re-clone and git apply the .patch, or fetch the branch from the bundle.

Push / open the PRs

  1. Fork both repos on GitHub.
  2. wine (set the PR base branch to hacking/validiy-sensor):

    cd /tmp/opencode/wine-validity            # or your own clone of the fork
    git remote add fork git@github.com:<you>/wine.git
    # only if /tmp was cleared:
    # git fetch /path/to/uunicorn-wine-modern-toolchain.bundle modern-toolchain-build-fixes:modern-toolchain-build-fixes
    git push -u fork modern-toolchain-build-fixes
    

    PR: https://github.com/uunicorn/wine/compare/hacking/validiy-sensor...:wine:modern-toolchain-build-fixes?expand=1

  3. sandbox:

    cd work/synaWudfBioUsb-sandbox
    git remote add fork git@github.com:<you>/synaWudfBioUsb-sandbox.git
    git push -u fork argv-dispatch
    

    PR: https://github.com/uunicorn/synaWudfBioUsb-sandbox/compare/master...:synaWudfBioUsb-sandbox:argv-dispatch?expand=1

  4. Paste the title/body from 01-... / 02-... above into each PR form.

  5. Notes

    • None of the drafts are submitted yet; review/edit the wording first.
    • 02 is honest about not being compile-tested (WDK headers needed); 01 and 03 were exercised on real 06cb:0081 hardware, respectively via a full verify run (03: the native route remains blocked by the dispatch-map NULL).
    • Our own repo notes the same content in README.md → "Contributing back".