[gs-commits] ghostpdl branch, nobble-cal, updated. jbig2dec-0.14-1663-g01d2084
[email protected] (Robin Watts)
| Newsgroups | gmane.comp.printing.ghostscript.cvs |
|---|---|
| Message-ID | <[email protected]> |
The ghostpdl branch, nobble-cal has been updated
discards 908d047570b6a106e6b34b052eb2e3c3860f12bf (commit)
via 01d2084a216f1d4b206faa309be6c509c445b4e7 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (908d047570b6a106e6b34b052eb2e3c3860f12bf)
\
N -- N -- N (01d2084a216f1d4b206faa309be6c509c445b4e7)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
----------------------------------------------------------------------
commit 01d2084a216f1d4b206faa309be6c509c445b4e7
Author: Robin Watts <[email protected]>
Date: Thu Sep 12 10:48:49 2019 +0100
Simple commit to avoid CAL being used; for cluster testing.
diff --git a/Makefile.in b/Makefile.in
index 8e36018..dd5e0df 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -200,7 +200,8 @@ SANITIZEDIRPREFIX=san
PGDIRPREFIX=pg
# Are we include the CAL library?
-WITH_CAL=@WITH_CAL@
+#WITH_CAL=@WITH_CAL@
+WITH_CAL=0
CALSRCDIR=@CALSRCDIR@
CAL_CFLAGS=@CAL_CFLAGS@
CAL_SSE4_2_CFLAGS=@CAL_SSE4_2_CFLAGS@
Summary of changes:
Makefile.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)