[gnome-continuous] Tag hunspell to latest release
- From: Emmanuele Bassi <ebassi src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-continuous] Tag hunspell to latest release
- Date: Thu, 7 Sep 2017 09:59:32 +0000 (UTC)
commit a25822fa3012833702ec9de9a156b05536456a47
Author: Emmanuele Bassi <ebassi gnome org>
Date: Thu Sep 7 10:58:03 2017 +0100
Tag hunspell to latest release
Apparently, the master branch is perfectly suited for landing commits
like this:
https://github.com/hunspell/hunspell/commit/d2a29f839c51fe8ddc964594e76d9b08ab04b10a
Followed by:
https://github.com/hunspell/hunspell/commit/46e0d8909c93f5743b4abb9a1e3255c91d17f6d4
according to the hunspell developers.
manifest.json | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
---
diff --git a/manifest.json b/manifest.json
index 7091c19..417b5aa 100644
--- a/manifest.json
+++ b/manifest.json
@@ -842,6 +842,8 @@
{"src": "git:https://chromium.googlesource.com/webm/libwebp"},
{"src": "git:https://github.com/hunspell/hunspell.git",
+ "tag": "2730ad3d32d839f439ba7f286e3600cd9294a978",
+ "tag-reason": "Use latest stable tag; hunspell devs think master is perfectly fine for
experiments",
"patches": ["hunspell-autogen.patch"]},
{"src": "tarball:http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz",
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]