Re: Issue 1964 in lilypond: lilydev 2.0

[lilypond]

Comment #12 on issue 1964 by address@hidden: lilydev 2.0
http://code.google.com/p/lilypond/issues/detail?id=1964

No, all work should be done based on master, and since contributors don't  
have git access, they don't need to worry about staging.  The basic  
workflow for them is still
1. update source from git master
2. edit
3. make patch
4. send patch to somebody


Your second suggestion is interesting, but AFAIK you can only run lilypond  
from the build dir when you're actually *in* the build dir -- otherwise it  
doesn't pick up the right materials in /share/.