Programming

18672 readers

108 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

Git without a forge (www.chiark.greenend.org.uk)

submitted 3 days ago by [email protected] to c/programming

17 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 2 days ago (1 children)

Do you mean sending patches by email? The author for the article also despises them as suggest alternatives for collaboration where you do "pull request" by people giving you a link to their repo and branch name (like literally asking you to try pulling from their git repo), or sending git bundle files which get around a lot of the problems of trying to send patch files around.

[–] KindaABigDyl 3 points 2 days ago* (last edited 2 days ago) (2 children)

Yes. The only way to send patches without something like Github is over email. I don't mind all the other stuff, but there's no other way to do PRs than over email, and I hate email. I didn't see that he gave alternatives. His preferred solution was an email

The formal PR button in a forge is a way to do that with one click, but a short email with all the same information is just as good.

Like, dawg, no it aint

[–] [email protected] 1 points 1 day ago* (last edited 1 day ago)

They meant mail. With patches in punch cards. Just as good.

[–] [email protected] 4 points 2 days ago

Email isn't "the only way" to send patches. In fact, he addresses that:

It doesn’t have to be by email, either. Any method of sending this data to the maintainer is fine. For example, I’m on Mastodon – so you could send me a repository URL via Mastodon if you really wanted to (provided you didn’t mind my responses being very short). Or you could send patches via any other communications medium that you and the maintainer are both on, if it lets you attach files to messages.

His preferred method is just sending a URL over email. You can use any communication method if you both already have an account.