From e414da695323cc0c606349d3e64b952aaf213776 Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Tue, 10 Aug 2010 16:33:48 +0100 Subject: [PATCH] Doc: CG: add instructions for renaming a snippet. --- Documentation/contributor/lsr-work.itexi | 26 ++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/Documentation/contributor/lsr-work.itexi b/Documentation/contributor/lsr-work.itexi index e1e770a560..01b136a470 100644 --- a/Documentation/contributor/lsr-work.itexi +++ b/Documentation/contributor/lsr-work.itexi @@ -8,6 +8,7 @@ * Approving snippets:: * LSR to Git:: * Fixing snippets in LilyPond sources:: +* Renaming a snippet:: * Updating LSR to a new version:: @end menu @@ -218,6 +219,31 @@ In any case, commit all changes to Git. @end enumerate +@node Renaming a snippet +@section Renaming a snippet + +Due to the potential duality of snippets (i.e. they may exist both +in the LSR database, and in @code{Documentation/snippets/new/}), +this process is a bit more involved than we might like. + +@enumerate +@item +Send an email LSR editor, requesting the renaming. + +@item +The LSR editor does the renaming (or debates the topic with you), +then warns the LSR-to-git person (wanted: better title) about the +renaming. + +@item +LSR-to-git person does his normal job, but then also renames any +copies of the snippets in @code{Documentation/snippets/new/}, and +any instances of the snippet name in the documentation. + +@code{git grep} is highly recommended for this task. + +@end enumerate + @node Updating LSR to a new version @section Updating LSR to a new version -- 2.39.5