5 ms·
I love this. This is how it was done back in the days of usenet. People would email patches to the linux kernel. Hackers, working alone, late at night, strange
by keepamovin 3y ago
I love this. This is how it was done back in the days of usenet. People would email patches to the linux kernel. Hackers, working alone, late at night, strange times, strange places. Cultivating their work and skills and then ... shoot ... sending an email! Their contribution. So cool!
Maybe we should go back to this. Get rid of the whole github thing. Every group their own little mailing list. Laboring in private!
- dewey 3y ago> Hackers, working alone, late at night, strange times, strange places. Cultivating their work and skills and then ... shoot ... sending an email! Very poetic, but also not much different to the current state. Just clicking to open a PR instead of sending an email attachment.
- nkjoep 3y agocorrect. Opening a PR triggers an email. No difference at all.
- keepamovin 3y ago:) Thank you! I guess I prefer text. And deeply there's a difference between staying in text, and moving to GUI. The medium is the message^0, and even if the process is "the same", everything becomes different because you're no longer within the text world. 0: https://en.wikipedia.org/wiki/The_medium_is_the_message https://en.wikipedia.org/wiki/The_medium_is_the_message
- dewey 3y agoI know it's not the same, but that's also why I prefer GitLab's "--push-option=merge_request.create" which creates a PR from the CLI without needing me to open the website and clicking a button. I'm still annoyed daily that this doesn't exist for GitHub.
- pjm331 3y agoGitHub has a CLI https://cli.github.com/manual/gh_pr_create https://cli.github.com/manual/gh_pr_create
- dewey 3y agoYes, but the advantage with the "push options" is that I can put it in my .gitconfig and it just works automatically when I do a git push without using some proprietary platform's cli.
- dnsmichi 3y agoThanks for sharing. GitLab team member here. More GitLab push options are documented in https://docs.gitlab.com/ee/user/project/push_options.html https://docs.gitlab.com/ee/user/project/push_options.html You can also add a parameter to merge the merge request when the pipeline succeeds. This can be handy for quick fixes that do not require reviews, and avoids unnecessary context switches. # mwps BRANCHNAME alias mwps='git push -u origin -o merge_request.create -o merge_request.target=main -o merge_request.merge_when_pipeline_succeeds' Example from https://gitlab.com/sytses/dotfiles/-/blob/master/git/aliases.zsh?ref_type=heads#L24 https://gitlab.com/sytses/dotfiles/-/blob/master/git/aliases... and https://about.gitlab.com/blog/2021/10/19/top-10-gitlab-hacks/#create-with-confidence https://about.gitlab.com/blog/2021/10/19/top-10-gitlab-hacks... If you prefer deeper CLI integration, suggest installing the GitLab CLI: https://docs.gitlab.com/ee/editor_extensions/gitlab_cli/ https://docs.gitlab.com/ee/editor_extensions/gitlab_cli/
- yankput 3y agosr.ht does that I don’t find it very user friendly (well, at all), but if you want a git forge that does that, you can use it.
- junon 3y agoThis is my experience as well. I love the hacker culture associated with it and it's very fun to use e.g. Mutt, sr.ht, and git-send-email together, but it's anything but efficient and straightforward. I ultimately moved away from sr.ht for that reason.
- ploum 3y agoSome, like myself, find the mouse really painful to use and hate graphical interfaces when you have to randomly click to find something (while you can read a man page, grep through it and then automatize the process in custom scripts). But it is not only about efficiency. It is about control and centralisation. Git-send-mail works everywhere there’s an email. It allows people to use the tool they prefer. It allows them to build custom tools. It doesn’t make people dependent from a forge (you are a simple "git remote set-url" away from using a new forge). Github forces everybody to use the same graphical interface which requires tons of JS and lot of CPU. Github forces you to accept all their changes. Github forces you to be a slave of Microsoft and contribute all your code to their IA training set. Github forces you to be notificed of stuff you don’t care. The "Hacker culture" is first and foremost about personal freedom. And if you believe the tool are not efficient, as a true hacker, you will built others (but, spoiler, most of the time, when you become proficient enough to build you own tools, you realize how efficient the existing ones are). Hacking is like walking. You look at walkers and you think it looks tiring to walk. So you go to the parking lot. You start your car. You go through the gate and give your driver license to the cop controlling you. You then go to the gas station. You pay with you credit card. There’s an accident in front of you, you are stuck in the traffic. You take your Google controlled GPS and ask for another itinerary. You drive. You wait at a red light, looking at your phone. A notification to pay the insurance of the car. Another one to pay for the leasing of the car itself. A light blink on the dashboard: you need to add oil and do the annual checkup of the car. You drive, you are a bit stressed and go too fast. You see a flash. Shit! Will I get a ticket? I was not that fast? You arrive at destination. There’s no room left in the parking. You start to drive around, hoping for a spot. There! You get it. It is bit small. You hope that nobody will scratch your car. For whatever reason, you learned that cars can’t be scratched so you are very careful. You get out of the car and walk a bit to the destination. Then you see them… The walkers. They went here by foot, through a path in the forest. They are smiling, even if they was some light rain. And you ask them: "Why don’t you guys get a car? Seriously? Walking is hard and inefficient. I can’t walk myself for than 1km before getting my legs sore."
- terminalcommand 3y agoMany oss projects still do this, don't they. I am subscribed to debian and python mail lists. Debian's lists are highly active.
- rightbyte 3y agoE.g. GCC does it by mail.
- keepamovin 3y agoI guess there must be a reason for that! It could just be most are used to that way, but I'd like to believe it's somehow "better"! haha :)
- nine_k 3y agoIf it was so long ago, it likely predates git, and was more painful than it is now. (Git was introduced in 2005, while Linux was first released in 1991; fourteen years separate them.)
- keepamovin 3y agoIndeed, you're right! Yet people still sent patches over email back then, and that is what I meant with "this was how they did it"! :)
- nine_k 3y agoAFAICT projects like OpenBSD still use the same infra: emailed patches and CVS (!).
- keepamovin 3y agoIndeed they do. There's impressively many heavy-duty projects that use it. A great many OSes. There's certainly something to it! :)
- nine_k 3y agoCertainly! For one thing, CVS does not allow for such easy rebases and merges as git, so someone has to read your patch carefully, make certain that it merges cleanly, and otherwise pay more attention. This may result in a slower pace, but also in less breakage and a larger shared understanding.
- keepamovin 3y agoNice! Yeah, CVS, I don't know much about it, but your comment reminds me I should check out things outside the git ken! They might just have valuable understandings I need to learn! Thanks for letting me know about it :)
- 3y ago
- mikemcquaid 3y agoDid you contribute to open source in those days? I did a little (KDE patches to mailing lists before I got Subversion access) and: it was _awful_. You think merging/rebasing/resolving conflicts is a pain now? Doing the same thing via email was _so_ much worse. GitHub has made some parts of open source worse (e.g. how easy it is to now open poor issues while ignoring required information compared to Bugzilla) but the contribution side is so much nicer now. (Bias/context: former GitHub employee, former KDE committer, current Homebrew project leader)
- dustfinger 3y ago> You think merging/rebasing/resolving conflicts is a pain now? Doing the same thing via email was _so_ much worse. Email is just used to receive the patch, you should use a tool meant for the job to actually do the merge. I realize that is probably not what you meant though. Besides, when email patching first began, the tooling was in its infancy. However; today tools like the git cli itself, or magit + smerge-mode (my personal preference) are as good as GitHub, if not better. I never actually use GitHub for merging, even when working on projects hosted in GitHub.
- beepbooptheory 3y agoSpent a long time not even knowing you can resolve merges in github. All I knew was magit and smerge, and assumed people with the fancier editors had something similar.
- mikemcquaid 3y ago> Email is just used to receive the patch, you should use a tool meant for the job to actually do the merge. I know because I also actually did this. You still had to do this locally and then turn it into an email and had no real indication whether someone else had seen/tried/reviewed/etc. it > However; today tools like the git cli itself, or magit + smerge-mode (my personal preference) are as good as GitHub, if not better. I can totally believe for you: this is the case. For most people, though: it will not be. Feel free to prove me wrong by creating a(nother) project that gets thousands of contributors entirely through email. (If you're actually Linus Torvalds, though: you win, I'll shut up now)