aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar Jan Mulder <jlmulder@xs4all.nl>2017-10-28 09:01:14 +0200
committerGravatar Jan Mulder <jlmulder@xs4all.nl>2017-10-28 09:05:16 +0200
commitbdf6dc78281bec2953c7a48f506895c192abd43a (patch)
tree016472526b7fa3a8811fb93625baa536900f5122
parent1095b7807147fa6f6ad74ed3a3c9b65106ccf2a0 (diff)
downloadsubsurface-bdf6dc78281bec2953c7a48f506895c192abd43a.tar.gz
Kirigami: newer SHA
Switch to a newer SHA, so that at least my commit is in. Checked the newer version, and no other artefacts seen. I think we should try to follow master where we can (but controlled). Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
-rwxr-xr-xscripts/mobilecomponents.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/mobilecomponents.sh b/scripts/mobilecomponents.sh
index 1bd14a98b..5a1fec025 100755
--- a/scripts/mobilecomponents.sh
+++ b/scripts/mobilecomponents.sh
@@ -33,7 +33,7 @@ if [ "$NOPULL" = "" ] ; then
git checkout master
git pull origin master
# if we want to pin a specific Kirigami version, we can do this here
- git checkout 6a16e00a692914b1d3918ba57e658342de4d2c23
+ git checkout 162b877ad4b03d4843e21e7e4674f5b74c7688fe
popd
fi
if [ ! -d breeze-icons ] ; then