commit: bc3b9f02969aa69e8bfd0f49b496b922d65e3583 Author: Sam James <sam <AT> gentoo <DOT> org> AuthorDate: Thu Dec 11 21:42:25 2025 +0000 Commit: Sam James <sam <AT> gentoo <DOT> org> CommitDate: Thu Dec 11 21:43:22 2025 +0000 URL: https://gitweb.gentoo.org/proj/rust-patches.git/commit/?id=bc3b9f02
README.rst: update description of scheme We use _pN for patchset changes on the ebuild side and _pN in git tags matching that. We use -N in the tags for non-revbump changes. Bug: https://bugs.gentoo.org/967342 Signed-off-by: Sam James <sam <AT> gentoo.org> README.rst | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/README.rst b/README.rst index 9999e72..a652887 100644 --- a/README.rst +++ b/README.rst @@ -15,8 +15,16 @@ Usage A branch will be created for each new Rust release (e.g. ``1.88``), and patches will be added to that branch as needed. Tags for ``${PV}`` will be created for each release, e.g. ``1.88.0``, ``1.88.1``, etc., to track the specific versions of -Rust that these patches apply to. Revbumps will be tagged as required - if a patch is added or updated, a tag will be -created for the new version (e.g. ``1.88.0-r1``). +Rust that these patches apply to. + +If a revbump is required on the ebuild side, please use _pN for the git tag +in rust-patches.git, e.g. `1.88.1_p1`. + +If a revbump is NOT required, and you're fixing a compile error or whatever, +please use '-N' for the git tag in rust-patches.git, e.g. `1.88.1-1`. + +We do NOT use `-rN` in the tags here to avoid confusion when we need to +revbump the Rust ebuilds for an unrelated reason. ``master`` will contain patches required for ``nightly`` (live / ``9999``) ebuilds and will be updated as needed.
