staging/ldir/scripts/env, branch masterKevin D-Bs staging treehttps://git-03.infra.openwrt.org/openwrt/staging/ldir/atom?h=master2021-11-13T20:29:41Zscripts/env: fix env for git conf init.defaultBranch not set to "master"2021-11-13T20:29:41ZArne Zachlod2021-11-10T13:47:55Zurn:sha1:b5ab6d0bc577e81a77f39211883f6c0c4155b6ed
Since version 2.28, git has a config option init.defaultBranch to set the name
of the first branch created with git init. The env script expects this name to
be "master". This commit sets the initial branch name to "master"
instead of using the git configured one.
Signed-off-by: Arne Zachlod <arne@nerdkeller.org>
scripts/env: Fix 56f813674a scripts/env: use command -v instead of which2020-07-12T12:29:28ZKevin Darbyshire-Bryant2020-07-12T12:25:39Zurn:sha1:8242c6de29951fbb549355770cd685ffe3ac9c54
We don't need to see how git will be executed and it produces non silent
output on 'scripts/env diff' commands when there are no differences
unlike before.
Re-introduce original silent behaviour.
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
scripts/env: fix remaining shellcheck warning2020-07-11T11:33:28ZPetr Štetiar2020-07-11T11:20:34Zurn:sha1:227e47b3ca964939f41c3564dd7da72d60044d00
Fixes following shellcheck warning:
In scripts/env line 25:
exit ${1:-1}
^-----^ SC2086: Double quote to prevent globbing and word splitting.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
scripts/env: use read -r instead of read2020-07-11T11:33:28ZRosen Penev2020-01-06T02:32:38Zurn:sha1:5b7cace9e3f553ca54e1e0ec5f7651b7d7a2052d
read mangles backslashes.
Found with shellcheck.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
scripts/env: exit in case of failure to cd2020-07-11T11:33:28ZRosen Penev2020-01-06T02:32:37Zurn:sha1:f80a540dbf9bf87e15f0f29da7f4019064ee207d
Found with shellcheck.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
scripts/env: replace \! with !2020-07-11T11:33:28ZRosen Penev2020-01-06T02:32:36Zurn:sha1:e68810ba5352d7db89a9975f2a2a8951fc9d5b2b
The latter is more standard. The former throws an error under
shellcheck.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
scripts/env: use command -v instead of which2020-07-11T11:33:28ZRosen Penev2020-01-06T02:32:35Zurn:sha1:56f813674a912490df327304033bf667b285930a
Simpler and built in to the shell.
Found with shellcheck.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
scripts/env: replace -a and -o with &&/||2020-01-02T22:56:19ZRosen Penev2020-01-01T02:01:43Zurn:sha1:995378a2a56d132594834a31c370d877c7d46d5c
The former are not well defined.
Found with shellcheck.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
scripts/env: use explicit find location2020-01-02T22:51:45ZRosen Penev2020-01-01T02:01:42Zurn:sha1:2fe5319d587c9c66ecbd7acbd5efbc1ff6fac8a8
Some find binaries do not imply the current directory.
Found with shellcheck.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
env: only use color diffs on terminals2018-05-05T07:44:43ZPhilip Prindeville2018-04-10T22:57:06Zurn:sha1:e495a050693952956a81847669b8b7888b4cd769
When sending script/env diff's output to a file or pipeline, you
don't want escape characters for ANSI color sequences fouling the
byte stream.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>