[FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org

[Jacob Lifshay]

On Thu, Jul 24, 2025 at 8:40 PM compn <ff at hawaiiantel.net> wrote:
> people can always just manually attach patches to emails sent to
> ffmpeg-devel list. no need for git send mail.

ok, I prefer to never do that though because it makes reading the
patches very annoying. Anyone should be able to read the patches
without having to download files and open them in their editor (which
is particularly annoying on phones), leaving a bunch of unwanted files
around when you're done reading. Yes, I know there's patchwork, but
that's also annoying to get to from the corresponding email since
there's no links to it from the patch email, so you have to go to the
website and search for the patch series you were trying to read.

> also i'm sure whatever development toolset you use can be scripted to
> send a patch via email?

sending emails from my command line is the majority of the annoyance,
since however I do that requires essentially the same steps as setting
up git send-email.

> are you using github or some other non command
> line git to write code?
no, just using git on Debian 12.

> maybe there is an easier workflow for you if
> git send-email is not to your liking?

yes, git push to a new branch, then click on the link to create a new
PR. (hence why I like code.ffmpeg.org)

> thanks for detailing out how other projects do it though, we are
> always looking to improve.

thanks for trying to improve!

Jacob