Robin H. Johnson
2024-Oct-14 19:45 UTC
How to actually get patches accepted? ATTN maintainers
Hi, This is mostly intended for the maintainers to read. What's intended way to actually get patches merged into rsync? I've tried: - Mailing list posts - GitHub PRs --ignore-non-existing-directory https://lists.samba.org/archive/rsync/2015-November/030455.html https://github.com/RsyncProject/rsync-patches/issues/8 https://github.com/RsyncProject/rsync/pull/595 TCP options: https://github.com/RsyncProject/rsync/pull/514 https://github.com/RsyncProject/rsync-patches/issues/9 I didn't use the Samba bugzilla, because it seems dead (For 2024, the entire rsync product has 4 bugs that changed). -- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation Treasurer E-Mail : robbat2 at gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 1113 bytes Desc: not available URL: <http://lists.samba.org/pipermail/rsync/attachments/20241014/66ee25a7/signature.sig>
Maybe Matching Threads
- Code inconsistency between release version and git in rsync-3.0.9
- Code inconsistency between release version and git in rsync-3.0.9
- [PATCH] Update header locations for uapi & generated
- [PATCH] Update header locations for uapi & generated
- [PATCH] Update header locations for uapi & generated