Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Gyan Doshi <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] doc/fate: document setting of session-wide env variables (PR #20930)
Date: Sun, 16 Nov 2025 04:57:28 -0000
Message-ID: <176326904978.25.5056954195665336501@2cb04c0e5124> (raw)

PR #20930 opened by Gyan Doshi (GyanD)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20930
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20930.patch

Revision of FFmpeg/FFmpeg!20907


>From e76fcf822346b47c6ec65ec59945ab896c16f193 Mon Sep 17 00:00:00 2001
From: Gyan Doshi <ffmpeg@gyani.pro>
Date: Sun, 16 Nov 2025 10:24:38 +0530
Subject: [PATCH] doc/fate: document setting of session-wide env variables

---
 doc/fate.texi | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/doc/fate.texi b/doc/fate.texi
index 57268d44b4..12c884047c 100644
--- a/doc/fate.texi
+++ b/doc/fate.texi
@@ -65,7 +65,7 @@ make fate
 See @ref{makefile variables} for a list of arguments that can be added.
 
 If you did not set the samples path during configuration, or if you wish to
-override it just before starting FATE, you can do so in one of two ways.
+override it just before starting FATE, you can do so in one of three ways.
 
 Either by setting a make variable:
 
@@ -74,7 +74,15 @@ make fate-rsync SAMPLES=/path/to/fate-suite
 make fate       SAMPLES=/path/to/fate-suite
 @end example
 
-or by prepending an environment variable:
+or by setting an environment variable for the current session:
+
+@example
+export FATE_SAMPLES=/path/to/fate-suite
+make fate-rsync
+make fate
+@end example
+
+or in isolation for a single command by prepending it:
 
 @example
 FATE_SAMPLES=/path/to/fate-suite make fate-rsync
-- 
2.49.1

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

                 reply	other threads:[~2025-11-16  5:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=176326904978.25.5056954195665336501@2cb04c0e5124 \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=code@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