Email or username:

Password:

Forgot your password?
Hector's posts Post Back to profile
Top-level
Karl

@marcan Curious to know what arguments are in favor of email patches.

Modern front-ends for git servers are literally providing an equivalent feature set but more convenient.

14 Feb 2023 at 16:28 | Wall-to-wall | Open on infosec.exchange
14 comments
Hector Martin

@karl "I can do patch reviews from Emacs"

Stuff like that.

14 Feb 2023 at 16:36 | Open on social.treehouse.systems
Arnaud

@marcan @karl Well I can review github PRs from vscode πŸ˜„

14 Feb 2023 at 16:47 | Open on mastodon.online
Ongion

@marcan @karl well, emacs is open source, so they should be able to add GitHub PR support to emacs themselves! πŸ˜‰

14 Feb 2023 at 16:59 | Open on mendeddrum.org
sirocyl

@marcan @karl my universal response for "but it wouldn't work in emacs" is "well then, fix emacs yourself, it's Free Software, you know, you're a capable programmer" in much the same vein that they argue whenever anyone else has an issue with free software. Ugh.

14 Feb 2023 at 17:01 | Open on social.treehouse.systems
Neal Gompa (ニール・ゴンパ) :fedora:

@marcan @karl I use Emacs. There are GitHub, GitLab, Pagure, Phabricator, and Gerrit clients for Emacs. You don't *have* to suffer through email for just that.

14 Feb 2023 at 17:16 | Open on fosstodon.org
Alyssa Rosenzweig πŸ’œ

@marcan @karl

I do GitLab patch reviews from vim, e-mail style... it annoys other devs sometimes but it's far better for everyone than e-mail πŸ˜…

14 Feb 2023 at 17:31 | Open on social.treehouse.systems
Karl

@marcan I haven't checked, but I'm sure there are some plug-ins out there that make emacs work with github/gitlab and friends.

If the other "reasons" given are of the same kind, it sounds to me like a disingenuous excuse to not change a workflow they have gotten used to. I am not impressed.

14 Feb 2023 at 17:32 | Open on infosec.exchange
LisPi

@karl @marcan All of which are individually incompatible and non-standard, complicating #interoperability.

#Email isn't amazing for sharing code, but neither are Github-style pull-requests.

We need something better than either of those two.

The centralized #API-driven workflow of #Github clones is also problematic because of what it does to #git as a #distributed system and its lack of resilience.

sourcehut.org/blog/2020-10-29-

14 Feb 2023 at 18:23 | Open on mastodon.top
LisPi

@karl @marcan A large part of that is entirely #git's fault, because #FossilSCM has no such problem (it has different ones instead mostly from its focus on cathedral development...).

Git's design insistence on carrying none of the other project metadata and tooling required for its use is a problem.

14 Feb 2023 at 18:31 | Open on mastodon.top
Go Up