Re: SOLVED

[Uwe Brauer]

   > That's great! 


   >     , but not sure about the structure of
   >     that patch



   >     (which git diff option to use


   > - You first need to rebase your local git area to emacs-25 as you are
   > planning to provide just a documentation patch, (otherwise you would
   > rebase to the master branch). 
   > - Then git commit the changes in your local area. 
   > - http://git.savannah.gnu.org/cgit/emacs.git/plain/CONTRIBUTE has
   > instructions on the style of writing commit logs. 
   > - Use git format_patch HEAD~1 to create patch for that last commit. 


   >     , to whom to send that patch


   > - You use the same M-x report-emacs-bug to describe the problem you
   > are solving along with the inline pasted patch you just created. 


   >     etc).


   > While you are at it, you can even initiate the process to finish the
   > copyright paperwork if you'd like to contribute more in future (why
   > not! :)); even though you don't need that right now for 3 lines of
   > documentation patch. 

   > I see that you heavily contribute to matlab-mode.el. Thanks for
   > maintaining that! And as Stefan Monnier mentioned in an earlier email
   > thread, that could possibly be integrated into octave-mode.el piece
   > by piece and be part of Emacs. 

   > Hope this helps. 
   > --

BTW, so the manual is a bit outdated and maybe it should be upgraded,
what do you think?.....

BTW which MUA are you using, because I have problems (using gnus) to
separate your response from my text (your are not the first one though)
the quotations with > seems flawed.