From: "J. Dekker" <jdek@itanimul.li>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v3 3/5] configure: switch to shebang without space
Date: Tue, 09 Apr 2024 16:03:20 +0200
Message-ID: <87jzl6r5tk.fsf@itanimul.li> (raw)
In-Reply-To: <76b4a6c4-555e-f1d-ff65-d5f0dbf2c852@martin.st>
Martin Storsjö <martin@martin.st> writes:
> On Tue, 9 Apr 2024, J. Dekker wrote:
>
>> Note that the config.sh file is left without a shebang, this file is
>> supposed to be sourced into the current environment.
>>
>> This commit is purely cosmetic.
>>
>> Signed-off-by: J. Dekker <jdek@itanimul.li>
>> ---
>> configure | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Thanks, this set seems fine to me - the explanations seem good now. (I'd
> consider merging patches 3-5 though, but keeping the full commit message from
> patch 3).)
>
Thanks for review, pushed with 3-5 squashed.
--
jd
_______________________________________________
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:[~2024-04-09 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 13:50 [FFmpeg-devel] [PATCH v3 1/5] configure: simplify bigendian check J. Dekker
2024-04-09 13:50 ` [FFmpeg-devel] [PATCH v3 2/5] ffbuild/libversion.sh: add shebang J. Dekker
2024-04-09 21:52 ` Marth64
2024-04-09 22:27 ` Henrik Gramner via ffmpeg-devel
2024-04-09 22:52 ` Marth64
2024-04-09 23:00 ` Marth64
2024-04-09 13:50 ` [FFmpeg-devel] [PATCH v3 3/5] configure: switch to shebang without space J. Dekker
2024-04-09 13:55 ` Martin Storsjö
2024-04-09 14:03 ` J. Dekker [this message]
2024-04-09 13:50 ` [FFmpeg-devel] [PATCH v3 4/5] tests/fate.sh: " J. Dekker
2024-04-09 13:50 ` [FFmpeg-devel] [PATCH v3 5/5] doc/texidep: " J. Dekker
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=87jzl6r5tk.fsf@itanimul.li \
--to=jdek@itanimul.li \
--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