Frédéric Bron <frederic.b...@m4x.org> writes: >> If you are familiar with various linux utilities, you >> could follow the instructions here >> http://lilypond.org/doc/v2.15/Documentation/contributor/summary-for-experienced-developers > > Do you mean that with git-cl, I could submit a patch that would be > automatically added to staging if successful?
No. > Wouah! Impressive, I will try to make this work. It will have an issue opened for discussion, it will have your patch uploaded on Rietveld, it will notify the people looking at the tracker that something is up for review, offering tools for doing per-line criticism. There will be a semi-automatic procedure testing that your patch passes the regression tests, opening discussion if successful. At some point of time, the patch will likely be put onto a Countdown, and become pushable after a few days. Someone will still have to actually push it. After that is done and the next release has been made, the QA team will verify that your work is indeed contained in the release. So no, the patch will not get pushed automatically. But there is a lot of infrastructure organized around having code pass into LilyPond, with a number of people and automated procedures keeping care that things don't break and are reasonably transparent. Using git-cl will usually be the easiest way to make use of that infrastructure. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
