From 2a78ef01c4fc585f43f4e821b29e4be3fd5561b7 Mon Sep 17 00:00:00 2001 From: John Mandereau Date: Thu, 5 Mar 2009 02:33:07 +0100 Subject: [PATCH] Contributors' Guide: amend LSR instructions on advice from Carl D.S. --- Documentation/devel/lsr-work.itexi | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/Documentation/devel/lsr-work.itexi b/Documentation/devel/lsr-work.itexi index 44bca06b83..027052790f 100644 --- a/Documentation/devel/lsr-work.itexi +++ b/Documentation/devel/lsr-work.itexi @@ -129,13 +129,17 @@ head -1 input/lsr/@var{foo}.ly @end example @item -@strong{In case the snippet comes from LSR}, apply the fix to the snippet in -LSR and send a notification email to a LSR editor with CC to the -development list -- see @ref{Adding and editing snippets}. The +@strong{In case the snippet comes from LSR}, apply the fix to the +snippet in LSR and send a notification email to a LSR editor with CC +to the development list -- see @ref{Adding and editing snippets}. The failure may sometimes not be caused by the snippet in LSR but by the -syntax conversion made by @command{convert-ly}; in this case, fix -@command{convert-ly} or report the problem on the development list, -then run @command{makelsr.py} again, see @ref{LSR to Git}. +syntax conversion made by @command{convert-ly}; in this case, try to +fix @command{convert-ly} or report the problem on the development +list, then run @command{makelsr.py} again, see @ref{LSR to Git}. In +some cases, when some features has been introduced or vastly changed +so it requires (or takes significant advantage of) important changes +in the snippet, it is simpler and recommended to write a new version +of the snippet in @file{input/new}, then run @command{makelsr.py}. @item @strong{In case the snippet comes from} @file{input/new}, apply in -- 2.39.5