@coolboymew@shitposter.club #DOPEFISH LIVES
Really, a rather unexpected reference :)
Notices by divVerent (divverent@misskey.de)
-
divVerent (divverent@misskey.de)'s status on Monday, 06-Mar-2023 08:47:27 JST divVerent -
divVerent (divverent@misskey.de)'s status on Saturday, 18-Feb-2023 10:16:23 JST divVerent @alcinnz@floss.social @lightweight@mastodon.nzoss.nz I misunderstood, sorry. I had assumed "link to your fork" meant you expected me to add the necessary support into git, web browsers and webmail providers to support send-email.
But still, I rather strongly believe that email based workflow is rather bad. Being able to anchor comments at specific lines of code, and being able to track that they actually get resolved, is so much better than "every few days, the author posts a new version of the patch to the ML and I have to read it all from scratch again and compare to previous comments to see if the did not get forgotten".
Of course, this is my preference as project maintainer. If I need to send a patch to your project, I do not care about that, and to me it just matters that I can conveniently get the patch across. "Link to my fork" is quite certainly convenient enough to me. -
divVerent (divverent@misskey.de)'s status on Saturday, 18-Feb-2023 10:03:08 JST divVerent @alcinnz@floss.social @lightweight@mastodon.nzoss.nz But why, I can just use merge requests on gitlab and even get CI. I do not work on projects that are email only.
Github's PRs have some major issues though, so if you don't like them, fine. If I worked on your project, I would probably just get an extra email and use send-email. Of course it would be less secure than my actual email, but given these are merge requests, you are supposed to review them anyway and thus the danger if someone impersonates me is low.
Gerrit BTW is a nice approach to PRs - way more focused on the actual reviewing but in exchange less of a discussion forum than GitHub PRs. GitHub recently adopted some ideas for a more review focused workflow too, but it still has this huge general commit discussion thing in the main focus which probably should move into the background. -
divVerent (divverent@misskey.de)'s status on Saturday, 18-Feb-2023 09:45:53 JST divVerent @alcinnz@floss.social @lightweight@mastodon.nzoss.nz Nah. Pull/merge requests are MUCH more user friendly as few even have the ability to use git send-email nowadays.
Because it does not even integrate with email clients, even less so web mail, and most major providers stopped supporting standard SMTP long ago.
(E.g. also because standard SMTP does not support 2FA which we recommend everyone to set up, don't we?)
Now if git send-email could integrate with mailto handlers set up at browser or OS levels, that would be great...