>> What me drives crazy is the structure of the main git repository.
>> If you follow github style, the graph gets littered with zillions
>> of `merge request' commits, one per pull request, which makes it
>> quite hard to follow the development IMHO.
>
> It's true it can get annoying if you have lots of one-commit
> contributions.
I don't see a major simplification for the maintainer. The most
important action IMHO for contributing a patch is to rebase, ensuring
that the patch compiles with master. As far as I can see, github's
ticketing system doesn't allow to simply update the patch; instead,
you have to open a new ticket. Lilypond's two-level approach with
separating issues from actual patches gives more consistency here.
Please correct me if I'm wrong.
Werner
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
