From: compn <ff@hawaiiantel.net> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org Date: Thu, 24 Jul 2025 18:36:47 -1000 Message-ID: <20250724183647.00005956@hawaiiantel.net> (raw) In-Reply-To: <CAC2bXD4TtU_ebx9pVL0kv=krKwSR2ZY4WNmzx1W_XusU-E34gQ@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1895 bytes --] On Thu, 24 Jul 2025 20:58:19 -0700, Jacob Lifshay wrote: > On Thu, Jul 24, 2025 at 8:40 PM compn <ff@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. attaching text patches with the proper mime type or file extension (.txt) usually allows the email client to handle displaying it without having to do extra steps. see this email for example. i just did git diff > patch.txt , then attached patch.txt to this email, in my normal gui email client. > > 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) if you have suggestions of any workflows which make it easier for you or anyone else to contribute, let us know. much thanks :) -compn [-- Attachment #2: patch.txt --] [-- Type: text/plain, Size: 246 bytes --] diff --git a/README.md b/README.md index f8c23f2870..6b040ab05f 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -FFmpeg README +FFconvert README ============= FFmpeg is a collection of libraries and tools to process multimedia content [-- Attachment #3: Type: text/plain, Size: 251 bytes --] _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-07-25 4:37 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-22 3:53 Lynne 2025-07-22 8:44 ` Kacper Michajlow 2025-07-22 9:15 ` Jacob Lifshay 2025-07-25 3:40 ` compn 2025-07-25 3:58 ` Jacob Lifshay 2025-07-25 4:36 ` compn [this message] 2025-07-25 11:41 ` Nicolas George 2025-07-25 14:20 ` Kieran Kunhya via ffmpeg-devel 2025-07-23 4:05 ` Lynne 2025-07-22 15:01 ` Leo Izen 2025-07-23 4:01 ` Lynne 2025-07-22 23:04 ` Michael Niedermayer 2025-07-23 4:01 ` Lynne 2025-07-23 9:16 ` Michael Niedermayer 2025-07-23 9:39 ` Kieran Kunhya via ffmpeg-devel 2025-07-23 9:59 ` Michael Niedermayer 2025-07-23 10:02 ` Kieran Kunhya via ffmpeg-devel 2025-07-23 11:48 ` Nicolas George 2025-07-25 4:05 ` compn 2025-07-26 14:57 ` Michael Niedermayer 2025-07-23 9:38 ` Michael Niedermayer 2025-07-23 11:49 ` Nicolas George 2025-07-26 17:03 ` Derek Buitenhuis 2025-07-26 19:29 ` Timo Rothenpieler 2025-07-26 20:01 ` Derek Buitenhuis 2025-07-26 20:14 ` Timo Rothenpieler 2025-07-26 20:24 ` Kacper Michajlow 2025-07-26 20:29 ` Derek Buitenhuis 2025-07-26 20:41 ` Timo Rothenpieler 2025-07-26 20:45 ` Derek Buitenhuis 2025-07-26 21:07 ` Kacper Michajlow 2025-07-26 21:18 ` Timo Rothenpieler 2025-07-26 22:44 ` Michael Niedermayer 2025-07-26 22:57 ` Timo Rothenpieler 2025-07-26 22:48 ` Michael Niedermayer 2025-07-27 9:39 ` Nicolas George 2025-07-26 20:28 ` Derek Buitenhuis 2025-07-26 20:14 ` Kacper Michajlow 2025-07-26 20:23 ` Timo Rothenpieler 2025-07-26 20:29 ` Kacper Michajlow 2025-07-26 20:33 ` Derek Buitenhuis
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20250724183647.00005956@hawaiiantel.net \ --to=ff@hawaiiantel.net \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git