Live data from Hacker News

FFmpeg moves to Forgejo

code.ffmpeg.org

31–40 of 374 posts

Re: FFmpeg moves to Forgejo

#32

How exactly does mailing list contributions work? I've only ever seen a few urls of messages but they are extremely obtuse. You would need to click parent parent parent to get context on the message you originally read. I must be missing something and since mailing lists are dying, would love to understand this relic of the past.

You're supposed to use a proper email client which solves this problem. Sourcehut uses the email contribution workflow and has the documentation to support it; have a look at it:

https://man.sr.ht/git.sr.ht/#sending-patches-upstream

https://git-send-email.io/

https://git-am.io/

Re: FFmpeg moves to Forgejo

#35

The site doesn't load any css for me on mobile, is it really worth it not to use GitHub or gitlab?

It's pretty good on desktop. Report the bug and I'm sure they'll get to it

The CSS bug happened to me on desktop too (but went away after a refresh). It looks related to Anubis since the reason the stylesheet isn't applying is that it has HTML containing "Making sure you're not a bot!" prepended to it.

Re: FFmpeg moves to Forgejo

#37
Opening this site I get "Oh Noes! Invalid Response" with an anime girl.

Tried refreshing, opening in a private windows, same thing.

EDIT: tried it again and got to "Making sure you're not a bot" with the same cringey anime girl, then the site loaded without CSS. Tried one more time, finally it loaded.

EDIT 2: clicked on a link and I'm back to "Oh Noes!...".

Re: FFmpeg moves to Forgejo

#38

How exactly does mailing list contributions work? I've only ever seen a few urls of messages but they are extremely obtuse. You would need to click parent parent parent to get context on the message you originally read. I must be missing something and since mailing lists are dying, would love to understand this relic of the past.

You're supposed to use a proper email client which solves this problem. Sourcehut uses the email contribution workflow and has the documentation to support it; have a look at it: https://man.sr.ht/git.sr.ht/#sending-patches-upstream https://git-send-email.io/ https://git-am.io/

Thanks for the links!

Seems you have to remember what -v you are sending as you respond to feedback. Pretty troublesome... Glad ffmpeg is moving to a more modern solution.

Post reply on HN