+1
Am 05.12.21 um 23:17 schrieb John Ralls: > Geert, > > Reviewing and commenting a big patch with several commits touching several > files and keeping track of what's been changed between versions via an email > conversation isn't attractive to me, nor is trying to keep track of which > change-sets have been applied, rejected, or are waiting for revisions. > > Yeah, the linux kernel uses mailing lists and a huge posse of designated > maintainers for handling patches. There doesn't seem to be any documented > system for keeping track of the patches, just an exhortation to submitters to > rebase and resubmit frequently during the limited "merge windows" at the > beginning of each development cycle. It sure seems to me--and likely to most > everyone else in the FLOSS community--that learning to use GitHub or GitLab > as a prerequisite for patch submission is the less painful route. > > Regards, > John Ralls _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
