Gregory's Server@0leil And I support them with that. The very old workflow of creating patch/diff and sending that around is dark magic :) With issue and PR management a la Github/Gitlab/Gitea/Codeberg a lot has become a lot better.
|
6 comments
 @0leil Please do! I will also start a blogpost on how Discord etc mess up communication in a project (IMHO) by mixing synchronous and asynchronous communication together in a way that isn't helpful but, again IMHO, damaging to the flow.  @jwildeboer @0leil It sucks, period. A mail list/usenet gives you all anytime. @0leil @jwildeboer Per-commit review is a point that I hadn't considered. With GitHub's PR UI only making the end result of all commits together apparent, I could see someone introducing a security vulnerability in a commit, fixing it in another, and then tricking a packager into publishing the version with the vuln... @jfred @0leil @jwildeboer per-commit doesnβt make sense when you are just going to deliver all those commits in one PR, same effect as squashing commits when accepting the PR. Main issue I see is trying to do too much in one PR. @jwildeboer ah and before I forget, there's this tool called b4 now that aims at making patch sending for mailing lists a bit easier. I personally have switched to that for the last 1+ year, I am NOT looking back. git-send-email? I now say no no :) |
@jwildeboer well... it is **a** workflow... which has nothing in common to mailing list based contribution.
GitHub/GitLab's PR workflow is an absolute disaster/nightmare for per-commit/patch review. Gerrit does that a bit better with patchsets but it gets difficult to read pretty quickly, even with topics.
GitLab/GitHub is just NOT necessarily compatible with some project's workflow.
I actually wrote a multiple pages long email on why no GH/GL for Yocto a while back, maybe I should put it in an article so it's easier to explain everything instead of being limited to a few 100s of characters at once :)
@jwildeboer well... it is **a** workflow... which has nothing in common to mailing list based contribution.
GitHub/GitLab's PR workflow is an absolute disaster/nightmare for per-commit/patch review. Gerrit does that a bit better with patchsets but it gets difficult to read pretty quickly, even with topics.