From: Graham Percival Date: Wed, 25 Aug 2010 14:57:32 +0000 (+0100) Subject: Doc: CG: discuss scripts/.../update-patch-version X-Git-Tag: release/2.13.32-1~35 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=aa7289794fe0bfe49093a2355eadbccb7e10cb4d;p=lilypond.git Doc: CG: discuss scripts/.../update-patch-version --- diff --git a/Documentation/contributor/programming-work.itexi b/Documentation/contributor/programming-work.itexi index ef917b5afc..f22b6b1c43 100644 --- a/Documentation/contributor/programming-work.itexi +++ b/Documentation/contributor/programming-work.itexi @@ -1177,6 +1177,19 @@ of the file. In some cases, this will not be possible, so the rule will simply point out to the user that the feature needs manual correction. +@subsubheading Updating version numbers + +If a development release occurs between you writing your patch and +having it approved+pushed, you will need to update the version +numbers in your tree. This can be done with: + +@example +scripts/auxiliar/update-patch-version old.version.number new.version.number +@end example + +It will change all files in git, so use with caution and examine +the resulting diff. + @node Automatically update auxiliary information @subsection Automatically update auxiliary information