Re: [Audacity-manual] Role of Manual Manager [was: Tracking changes across pages]

[Gale A. <ga...@au...>]

| From Bill Wharrie <bi...@go...> 
| Sun, 26 Feb 2012 12:33:09 -0500
| Subject: [Audacity-manual] Role of Manual Manager [was: Tracking changes across pages]
> > On 26/02/2012, at 12:08 PM, Gale Andrews wrote:
> > Meantime there are things you can do to make checking inside
> > easier, for example search for: 
> > 
> >    _("
> > 
> > which should show you any string changes (if the line has a "+"
> > against it to indicate it is replacing the line that has a "-"
> > against it).   
> 
> Yes, for string changes. But there are functional changes that may 
> not involve a string change. For example r11478 "Tidy up equalization
> curve renaming logic so it is clearer what is going on." I can't tell
> from reading the code or the diff if this would require any changes in
> the manual, and haven't had a chance to try it out.

I would respectfully suggest that was a log message we could 
have improved on. =:) 

It is on my (endless) list too to check that renaming still works
OK. 

My reading is that doesn't affect the Manual at all. It is making the
logic clearer for a developer. 

If you go with this and it helps, I would be prepared for you to 
ask me (as far as I can tell) when you are unsure whether a
commit affects the Manual. 

James gave -1 to my suggestion of "affects Manual" in the log 
message. I can see a danger of assuming a message that did not 
have "affects Manual" did not affect it. Was that why the -1? 





Gale