Johannes Zellner 8b23cb756d Add upstream contribution drafts; generalize sandbox patch 1 ay önce
..
01-uunicorn-wine-modern-toolchain.md 8b23cb756d Add upstream contribution drafts; generalize sandbox patch 1 ay önce
02-uunicorn-sandbox-argv-dispatch.md 8b23cb756d Add upstream contribution drafts; generalize sandbox patch 1 ay önce
03-rstar000-synaTudor-progress.md 8b23cb756d Add upstream contribution drafts; generalize sandbox patch 1 ay önce
README.md 8b23cb756d Add upstream contribution drafts; generalize sandbox patch 1 ay önce

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

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).

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".