Just wanted to throw this observation out: the current work on optional arguments is one area where working with Rietveld is getting really strained. The reason is that Rietveld just supports discussing and improving a single patch/commit.
The current patch series consists of one infrastructure patch (allowing pushing tokens with values) and "the rest". But there are about five different other (co-developed) infrastructure patches that the whole depends on. Making those independent issues would mean that you could not apply the main Rietveld patch to origin/master and check it out. So my workflow when on a larger Rietveld-reviewed patch like this consists of silently pushing required infrastructure/cleanup patches without discussion or review in order to keep origin/master in a state where one can meaningfully discuss the large single patch on top without getting side-tracked in unrelated issues. That's not really pretty. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
