From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
by master.gitmailbox.com (Postfix) with ESMTPS id 515514CAC1
for <ffmpegdev@gitmailbox.com>; Tue, 13 May 2025 18:06:36 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 3A04968B5A1;
Tue, 13 May 2025 21:05:53 +0300 (EEST)
Received: from mail-pl1-f173.google.com (mail-pl1-f173.google.com
[209.85.214.173])
by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 5FDA668A633
for <ffmpeg-devel@ffmpeg.org>; Tue, 13 May 2025 21:05:40 +0300 (EEST)
Received: by mail-pl1-f173.google.com with SMTP id
d9443c01a7336-22fa48f7cb2so57261655ad.1
for <ffmpeg-devel@ffmpeg.org>; Tue, 13 May 2025 11:05:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1747159534; x=1747764334; darn=ffmpeg.org;
h=cc:to:mime-version:content-transfer-encoding:fcc:subject:date
:references:in-reply-to:message-id:from:from:to:cc:subject:date
:message-id:reply-to;
bh=kTQqpKwW4/Zir//ii6adlinIuaQ8lRLZTAQ681MqjxM=;
b=FR/dhNli+rSWjSn2Z55UnSE+P1AnAmxlpMzXS8OnCPME4Y2+YblciXcP8CKbWz/4Eg
DiWUdachZAsweYEOodkTbxkpY+xJCakFLVOAJsuOorn/4I1tVca3KmQHe/XAIKJtqt8B
Ryik//rgiVc5ntSzkPg8b5Xw3rwLZxp6I8Rz2XZTlQRsoJh1V8yQ5DxjQ/W55y+Kptxl
r7QCaEBSmFojnfcAThgWq1/gXgzO07/d+Dx5Gu3YXdQRKVQtg7rUOSlT5uqJ0K/jPcsm
F6gQr2nvVB8Hw0mo7K3VYhVkZmlP8xDH0OfKb8WKmfV/V/a1IfKgXHhY5bBXEhicXV3u
xCUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1747159534; x=1747764334;
h=cc:to:mime-version:content-transfer-encoding:fcc:subject:date
:references:in-reply-to:message-id:from:x-gm-message-state:from:to
:cc:subject:date:message-id:reply-to;
bh=kTQqpKwW4/Zir//ii6adlinIuaQ8lRLZTAQ681MqjxM=;
b=wVug+iwYtWLKwEmZExYPMvmuaKmd1rNvkQVlS79w3aOf45mQA3qyXazv7t6N6ywlaz
irzrtalF+4jVvSEwMetA3wNv9n4A22QDVVT4K7hJGyrxd4Brbc3aN0gh4xYV35iAe2Wg
J7Qi0z71O/qUOOGXxpmV665WWplPLfGiLWc4oDI0wJidaD94+XjpkO+dStQn4nqKutZ0
kCJa2MfMQUcaKwWl1GGkO6sMAejpH5Ic5VyaOAOSaBbpManPkQWkK5sTTitYZHmbOHYv
VImlv8A674x5ardlL+Z4Tlm1U/5VG1heodlk9munYhfzh0YvzZxxHCgKZErwx3RiAc72
dunQ==
X-Gm-Message-State: AOJu0Yx3wDpBg+FLjEkFLWbnZPGjRZFmDecIEhSIc3ofa0ji0k6fIbR3
dbI8VONiuOA23PxnQbOp2ml7DQQ1An/M6Bb1tMJ4g/r3gbSMOI2GZuBsug==
X-Gm-Gg: ASbGncuj4AjgYVaujp2bMCOwEe0L1AhGPO6dYTw65lNaBGg3V8Botjr8F5AExLmejr4
iHPKxyGrUA/NAaRBTk/8VtcjSqmpyRiWateW/aN8vY4t2rAMh8IJ/dWusDBlU+y9OEZ8Senp7cT
gUHsv1e2PlhL5t9PqjXLrm5EujvSg3gKF2Zwo4bvGssRWfAsJWPrLB4McwVxokFIXVdbgII1wBv
B86rAnRwjDdS5s3H5WhPiFxQvGZJW72k5pCp6s7O1/ZRapfLt1HerYv4t3PBroMV5VHwduI9HZa
bSXQy8AWbI0K6hzDJZp54s6kHeoaG5kbNbt2Mg35liVR8Kg35EdB7RpnZN0KnCVtzQUKdw==
X-Google-Smtp-Source: AGHT+IFJb1L1TQYdxk4D9tLn30dVax2NywrCRcOS1pqNY6WsWAUFMIiHUcJ48OLr1IHWn0Fhx5+IIg==
X-Received: by 2002:a17:903:b0e:b0:224:76f:9e4a with SMTP id
d9443c01a7336-23198119c40mr5365805ad.14.1747159534430;
Tue, 13 May 2025 11:05:34 -0700 (PDT)
Received: from [127.0.0.1] (master.gitmailbox.com. [34.83.118.50])
by smtp.gmail.com with ESMTPSA id
d9443c01a7336-22fc828b364sm84247835ad.172.2025.05.13.11.05.34
(version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
Tue, 13 May 2025 11:05:34 -0700 (PDT)
From: softworkz <ffmpegagent@gmail.com>
X-Google-Original-From: softworkz <softworkz@hotmail.com>
Message-Id: <866fd3aa3bde0d6e6bbdf1bee98b52ac6aef7f35.1747159511.git.ffmpegagent@gmail.com>
In-Reply-To: <pull.76.v2.ffstaging.FFmpeg.1747159511.ffmpegagent@gmail.com>
References: <pull.76.ffstaging.FFmpeg.1746699749.ffmpegagent@gmail.com>
<pull.76.v2.ffstaging.FFmpeg.1747159511.ffmpegagent@gmail.com>
Date: Tue, 13 May 2025 18:05:10 +0000
Fcc: Sent
MIME-Version: 1.0
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH v2 3/4] doc/developer: Reorder Submission
procedures content
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
<mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
<mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: softworkz <softworkz@hotmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/866fd3aa3bde0d6e6bbdf1bee98b52ac6aef7f35.1747159511.git.ffmpegagent@gmail.com/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>
From: softworkz <softworkz@hotmail.com>
Signed-off-by: softworkz <softworkz@hotmail.com>
---
doc/developer.texi | 48 ++++++++++++++++++++++++----------------------
1 file changed, 25 insertions(+), 23 deletions(-)
diff --git a/doc/developer.texi b/doc/developer.texi
index a723d41f39..5a026fff0e 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -752,10 +752,7 @@ We think our rules are not too hard. If you have comments, contact us.
First, read the @ref{Coding Rules} above if you did not yet, in particular
the rules regarding patch submission.
-When you submit your patch, please use @code{git format-patch} or
-@code{git send-email}. We cannot read other diffs :-).
-
-Also please do not submit a patch which contains several unrelated changes.
+Please do not submit a patch which contains several unrelated changes.
Split it into separate, self-contained pieces. This does not mean splitting
file by file. Instead, make the patch as small as possible while still
keeping it as a logical unit that contains an individual change, even
@@ -768,13 +765,6 @@ The tool is located in the tools directory.
Run the @ref{Regression tests} before submitting a patch in order to verify
it does not cause unexpected problems.
-It also helps quite a bit if you tell us what the patch does (for example
-'replaces lrint by lrintf'), and why (for example '*BSD isn't C99 compliant
-and has no lrint()')
-
-Also please if you send several patches, send each patch as a separate mail,
-do not attach several unrelated patches to the same mail.
-
@section Patch submission checklist
@@ -892,23 +882,35 @@ of leaks, out of array accesses, etc.
Patches should be posted to the
@uref{https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel, ffmpeg-devel}
-mailing list. Use @code{git send-email} when possible since it will properly
-send patches without requiring extra care. If you cannot, then send patches
-as base64-encoded attachments, so your patch is not trashed during
-transmission. Also ensure the correct mime type is used
-(text/x-diff or text/x-patch or at least text/plain) and that only one
-patch is inline or attached per mail.
-You can check @url{https://patchwork.ffmpeg.org}, if your patch does not show up, its mime type
-likely was wrong.
+mailing list.
+
+There are several ways how this can be accomplished:
-@subheading How to setup git send-email?
+@subsection Using @code{git send-email}: Git sends e-mail directly via SMTP
+
+@code{git send-email} will properly format and send
+send patches without requiring extra care if the required setup is feasible.
Please see @url{https://git-send-email.io/}.
+
For gmail additionally see @url{https://shallowsky.com/blog/tech/email/gmail-app-passwds.html}.
-@subheading Sending patches from email clients
-Using @code{git send-email} might not be desirable for everyone. The
-following trick allows to send patches via email clients in a safe
+
+@subsection With @code{git format-patch}: Sending patches from email clients
+
+You can create patch files via @code{git format-patch} and send them as inline
+text or as base64-encoded attachments, so your patch is not trashed during
+transmission. Also ensure the correct mime type is used
+(text/x-diff or text/x-patch or at least text/plain).
+
+If you send several patches, send each patch as a separate mail,
+do not attach several unrelated patches to the same mail.
+
+You can check @url{https://patchwork.ffmpeg.org}, if your patch does not show up, its mime type
+likely was wrong.
+
+
+The following trick allows to send patches via email clients in a safe
way. It has been tested with Outlook and Thunderbird (with X-Unsent
extension) and might work with other applications.
--
ffmpeg-codebot
_______________________________________________
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".