4 ms·
It's hard when you have lots of folks jumping into a code review, and you don't want to duplicate effort or you want to rapidly iterate on your code. You know
by jyrkesh 7y ago
It's hard when you have lots of folks jumping into a code review, and you don't want to duplicate effort or you want to rapidly iterate on your code.
You know those email chains that just continue to fork? Where people reply to the original (or the first couple replies) with their wall of text after a couple other replies have already trickled through?
That's what a collaborative, stateful PR solves.
- colbyrussell 7y agoEveryone is trying to get me to defend mailing lists. I have no idea why. I haven't said anything about them. In fact, I hate mailing lists.
- chinhodado 7y ago> I haven't said anything about them. > # now attach/upload bugfix.patch Where do you "attach" your patch file? Also, if it's not GitHub/GitLab/gerrit/reviewboard/etc. and not mailing list, what other workflow for code contribution are you talking about then?
- colbyrussell 7y agoI'm not going to be strawmanned for the third time in this conversation. I didn't say it wasn't GitHub/GitLab/gerrit/reviewboard/etc and not a mailing list. I said it's not a mailing list. This message board is a cesspool.