From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 8B00C4BE3D for ; Fri, 25 Jul 2025 04:37:05 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id A070F68D79F; Fri, 25 Jul 2025 07:37:00 +0300 (EEST) Received: from relay.b.hostedemail.com (smtprelay0038.b.hostedemail.com [64.98.42.38]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 8774A680459 for ; Fri, 25 Jul 2025 07:36:53 +0300 (EEST) Received: from omf07.b.hostedemail.com (omf07 [10.200.6.70]) by unirelay07.b.hostedemail.com (Postfix) with ESMTP id 4830A183AAF for ; Fri, 25 Jul 2025 04:36:52 +0000 (UTC) Received: from [HIDDEN] (Authenticated sender: ff@hawaiiantel.net) by omf07.b.hostedemail.com (Postfix) with ESMTPA id E466B160003 for ; Fri, 25 Jul 2025 04:36:49 +0000 (UTC) Date: Thu, 24 Jul 2025 18:36:47 -1000 From: compn To: ffmpeg-devel@ffmpeg.org Message-ID: <20250724183647.00005956@hawaiiantel.net> In-Reply-To: References: <20250722035337.2216565-1-dev@lynne.ee> <20250724174028.00001285@hawaiiantel.net> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/xLZRb6LSU53AXmL.YINutYz" X-Rspamd-Server: rspamout01 X-Rspamd-Queue-Id: E466B160003 X-Stat-Signature: 8gf1dfjaeusanw3gcdn78rytizqw6uh5 X-Spam-Status: No, score=-0.31 X-Session-Marker: 666640686177616969616E74656C2E6E6574 X-Session-ID: U2FsdGVkX1/18MwmcdjFn+t+I6ZdOJlpcx5Gix6+ja8= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hawaiiantel.net; h=date:from:to:subject:message-id:in-reply-to:references:mime-version:content-type; s=opensrs-2024012500; bh=bzt72ESVDvyEjUrGvpV+XyiaQONBtuTUig0dMgROg4M=; b=i+IPH9cCiyPz9F6y6igg0ixACPIzRb0ymgxeXGXohc+kydxdFobKZkCsnNJaujapmllWzHtIkPWcf/YTpuY2rFINmmcoFtK6PRBf+RixxcEo4CJtV9X6imPzHKB8vYq0SvQvRc9GiKKozIeWrfiT2pqioMs0rQu2aznE1jS2TBOEuW5k6BJOQl4qWOXEvE+9ydDN6OksGqx2q6uTkz5WudT87FyuFY5xQ1EheSg+tWRuCzJ+2Z7x3EB4wP8qjlhjT8ozmhRbxAhmx2SAD/qgEKz91cmkaSdkRXS7SsekV3YNvWw8VFx8sNyGdVKYx3kF3y/Ob6XQFMvxfYu7urFnOw== X-HE-Tag: 1753418209-231040 X-HE-Meta: U2FsdGVkX19P0PJHSe9hK00kDdDrOnwGJeSQy3SW5tiEksr/u5Bts4nSFG478IXZM1pUowmjj5V9SJMiJGgDETP3vo/cID7s6WdLEMj0KkDnQa2SIk3SeISm6jsuZ05qOndkMqx9euT+0vVX6ZukG8Y3AmYsbZzEN60Ij/2Sx/cju3I9c3iMk59v7gjRvjxCfKHvCNMuUFlkguG4lSM9Q7dwy+ioi2H17HQtD3q9wtN5AL3hqiWRfgkcM5oi3IOks9RP+nAWxFxQP74t9cHwcwSJbY7/lbJMKsDzXuobHzC6VmqUzv6UEV0ejf0V7Ra8LjMnz2epZ48DALJe4M1Si905sGVlH2KH0hFqD4yWR9c6WQofsDlGjJm3h42CAcureAyAzd1JaAzK7v3K+bfbIQbK0e4v0MYiFHkz/xj2HVmGYJXBgih0met5umw7B3JkzRwG/PoO7s92WlhveYi2Y6sp7eLdkY4jgh/O7D834rU= Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --MP_/xLZRb6LSU53AXmL.YINutYz Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 24 Jul 2025 20:58:19 -0700, Jacob Lifshay wrote: > On Thu, Jul 24, 2025 at 8:40=E2=80=AFPM compn wrote: > > people can always just manually attach patches to emails sent to > > ffmpeg-devel list. no need for git send mail. =20 >=20 > 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. =20 > > also i'm sure whatever development toolset you use can be scripted to > > send a patch via email? =20 >=20 > 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. >=20 > > are you using github or some other non command > > line git to write code? =20 > no, just using git on Debian 12. >=20 > > maybe there is an easier workflow for you if > > git send-email is not to your liking? =20 >=20 > 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 --MP_/xLZRb6LSU53AXmL.YINutYz Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=patch.txt 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 --MP_/xLZRb6LSU53AXmL.YINutYz Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --MP_/xLZRb6LSU53AXmL.YINutYz--