notmuch.git  about / heads / tags
Unnamed repository; edit this file 'description' to name the repository.
   commit 02a7b026d938f53d9fd9b183ca2b3c44c92489f2 (patch)
   parent bbe62623 NEWS: update for 0.31.2
     tree 0b089c56417949b64f48743c3fe84ebe7271a4d4
   author David Bremner <david@tethera.net>  2020-11-08 13:33:08 -0400
committer David Bremner <david@tethera.net>  2020-11-08 13:33:08 -0400

release: explicitely build sphinx-html

This is to force it to happen after the "make clean".
---
 Makefile.local | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Makefile.local b/Makefile.local
index 205fc9d3..fb126294 100644
--- a/Makefile.local
+++ b/Makefile.local
@@ -64,9 +64,10 @@ update-versions:
 # are part of the release and need to take the version from the
 # version file).
 .PHONY: release
-release: verify-source-tree-and-version sphinx-html
+release: verify-source-tree-and-version
 	$(MAKE) VERSION=$(VERSION) verify-newer
 	$(MAKE) VERSION=$(VERSION) clean
+	$(MAKE) VERSION=$(VERSION) sphinx-html
 	$(MAKE) VERSION=$(VERSION) test
 	git tag -s -m "$(PACKAGE) $(VERSION) release" $(UPSTREAM_TAG)
 	$(MAKE) VERSION=$(VERSION) $(SHA256_FILE) $(DETACHED_SIG_FILE)


glossary
--------
Commit objects reference one tree, and zero or more parents.

Single parent commits can typically generate a patch in
unified diff format via `git format-patch'.

Multiple parents means the commit is a merge.

Root commits have no ancestor.  Note that it is
possible to have multiple root commits when merging independent histories.

Every commit references one top-level tree object.

git clone https://yhetil.org/notmuch.git