From: Henrik Gramner via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Henrik Gramner <henrik@gramner.com>
Subject: Re: [FFmpeg-devel] [PATCH v3 2/5] ffbuild/libversion.sh: add shebang
Date: Wed, 10 Apr 2024 00:27:47 +0200
Message-ID: <CAFGUN0rfGXFAfCt6-dcfkRFEquzZHZUnF0VBDesz6tFsZJ6c1g@mail.gmail.com> (raw)
In-Reply-To: <CA+28BfCBE0UGiQffXGfifjUykcAHcPDxfs+=Eu33Ubmn6ErMxg@mail.gmail.com>
On Tue, Apr 9, 2024 at 11:52 PM Marth64 <marth64@proxyid.net> wrote:
> > +#!/bin/sh
> Might I suggest `#!/usr/bin/env sh` instead for this case?
> I tend to prefer it from a portability and usability perspective,
> but I can imagine for sh it might not matter.
/bin/sh exists on virtually every *NIX system whereas /usr/bin/env is
not ubiquitous, so that seems like a terrible idea that would achieve
the opposite result.
_______________________________________________
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 22:28 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 [this message]
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
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=CAFGUN0rfGXFAfCt6-dcfkRFEquzZHZUnF0VBDesz6tFsZJ6c1g@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=henrik@gramner.com \
/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