Append trick for propagating changes to live ebuild to docs

[genkernel.git] / HACKING

diff --git a/HACKING b/HACKING
index a2e197e5f6388fe91466bfdf542d5bf70864cd53..a802779ed12ae53af41717a7999fb33391335484 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -29,6 +29,7 @@ Rolling a release:
   - cp genkernel-${PV}.tar.bz2 /usr/portage/distfiles/
 - Bump the ebuild
 - Propagate ebuild changes to the live ebuild
+    diff genkernel-${OLD_PV}.ebuild genkernel-${NEW_PV}.ebuild | patch genkernel-9999.ebuild
 - check open bugs with keyword "InSVN" or "InVCS" for closability
   and close these bugs with a comment like "Fixed in ${PV}, just released.  Closing."
 - Send a mail with subject "genkernel ${PV} released" to both