Typo fix in NR
Issue 3719: CG: Add comment about git-cl editor

git-cl fires either the editor specified by the
EDITOR environment variable or vi if EDITOR isn't defined.
Commit mentions this in the CG

Signed-off-by: David Kastrup <dak@gnu.org>
Issue 2067: Give all of \display{LilyMusic,Music,Scheme} optional port arguments.
Web: updated Authors.itexi

All contributions since release of 2.17.0

Circa Aug 25 2012
Web: What we wrote... Book about LP in Turkish

Came from message

URL: http://lists.gnu.org/archive/html/bug-lilypond/2013-12/masg00051.html

Professor Server Acim's book in Turkish about LilyPond
Web: Improve notes about Linux Dist LP Packages

Issue 3735

Explain that LP in most Linux Repositories is going to be
older than the current available code on the LP website
Doc: Usage add .vimrc syntax highlighting

Issue 3492
Doc: Add @knownissue for AddLyrics with Nullvoice

Issue 3654
Issue 3748: Allow assignments with property paths to use x.y.z = value syntax

This is actually an embarrassing oversight in issue 2883: while it
became possible to rewrite

    markup-system-spacing #'minimum-distance = #25
as
    markup-system-spacing minimum-distance = #25

it has been overlooked to allow for the obvious

    markup-system-spacing.minimum-distance = #25
grob-property: if callback is independent of layout, call just once
Documentation/included/authors.itexi: remove Chong Yidong from core contributors

He crept in through a misinterpretation of a commit message.
Doc-it: translate footer and browser-language page
Merge branch 'translation' into staging
Issue 3732: Web: "Features": Modify outline

This doesn't modify the content, although I have a clear idea about it.
So some contents don't seem to fit to the headings.
Issue 3732: Web: Rewrite "Features" content

The "Features" page had some problematic content and structure.
This commit makes some points more clear, removes problematic
claims and introduces some more points pro LilyPond.

Additionally replace some "color2" divs by generic divClass
Update documentation for what's supported in MIDI. (issue 3740)

Also clarify what articulate.ly supports.

Change the snippet for redefining a shorthand to use an ArticulationEvent
instead of an articulation name, so users who follow its example will have
their articulations work in MIDI.
Match python/convertrules.py versions to that of stable branch.

This became necessary due to cherry-picking the following into stable:

convert-ly rule for new make-relative semantics accepting music arguments

This only works when the "reference pitch" is the first or last of
the list.

No attempt is made to rewind the version numbers of already converted
files from 2.19.0 to 2.17.97.
Issue 3746: Fix unfold-repeats-fully with alternatives

When fewer alternatives than repeats are given, the _first_ alternative
needs to get reused (the previous code wrongly used the last one).