summaryrefslogtreecommitdiffstats
path: root/package/libgtk3
diff options
context:
space:
mode:
authorYann E. MORIN <yann.morin.1998@free.fr>2018-04-17 18:48:21 +0200
committerThomas Petazzoni <thomas.petazzoni@bootlin.com>2018-04-19 22:32:28 +0200
commitd48a1b0d5e43c1dee5343f2d5dcbdc5808d8fb2b (patch)
treee421ba2f6d5b0b5f9fe26e6d02980bacb946f948 /package/libgtk3
parenta07da16e781d2be52a9a35490e1ab705d6f80cdf (diff)
downloadbuildroot-d48a1b0d5e43c1dee5343f2d5dcbdc5808d8fb2b.tar.gz
buildroot-d48a1b0d5e43c1dee5343f2d5dcbdc5808d8fb2b.zip
download/git: ensure we have a sane repository
There are cases where a repository might be broken, e.g. when a previous operation was killed or otherwise failed unexpectedly. We fix that by always initialising the repository, as suggested by Ricardo. git-init is safe on an otherwise-healthy repository: Running git init in an existing repository is safe. It will not overwrite things that are already there. [...] Using git-init will just ensure that we have the strictly required files to form a sane tree. Any blob that is still missing would get fetched later on. Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Reported-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Ricardo Martincoski <ricardo.martincoski@gmail.com> Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Tested-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Diffstat (limited to 'package/libgtk3')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud