What are advantages of it and also how said mailing list works? (In case of software development)
You must log in or register to comment.
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, itβs welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
Icon by @Double_A@discuss.tchncs.de
- 0 users online
- 254 users / day
- 965 users / week
- 2.45K users / month
- 5.6K users / 6 months
- 1 subscriber
- 3.07K Posts
- 119K Comments
- Modlog
Git was specifically CREATED to facilitate this exact mailing list workflow.
With git you donβt have to push and pull to a repo, it also works by sending signed commits over any method you want.
Linux development includes a large number of contributors who use email. Git was originally created specifically for Linux development so of course it caters to this approach.
Thereβs also the fact that the lead devs for Linux serve as a clearing-house for patches, so receiving them over email with explanations and everything helps them decide what makes it in.
Pull requests are not the only way of doing things. Generally speaking git can do a lot of workflows and architectures but most people are only familiar with gitflow and PRs.
I was under the impression it was primarily " if it isnβt broken, then donβt fix it" levels of tradition.
I could be wrong though, so if someone with more creds than a random internet dweller comes along, feel free to ignore me.
Heck, if you think Iβm an idiot, feel free to ignore me :)
Probably because it works and there hasnβt been a strong reason to change it.
It would work better under these modern methods, but the fallout during changing would be too much to handle
define better
Itβs obvious in the case of git, git development occurred before gitlab existed.