[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Some cherry-picks for stable/2.20
From: |
Knut Petersen |
Subject: |
Some cherry-picks for stable/2.20 |
Date: |
Fri, 12 Jul 2019 08:36:53 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 |
Hi everybody
I think some commits in master should be cherry-picked for stable/2.20:
git cherry-pick -x \
6e98e7e7b0d0ac46ba7e54f4b3946228f44fc414 \
9fb52ef2c93588192842fffa1b115c6f2d360321 \
f76997b5097f588060f823c4c87f01bac9f2fe50 \
b0300944e015b5957e50441224699e55c68c3dc3 \
a64b4dbc92ac0bbece08043349a55dccd84f4fd7
Reason: Our regression test code was broken in master and
still is broken in stable/2.20. We need the fix in issue 5467,
these are the last three of the five recommended commits.
The last three commits change scm/framework-ps.scm and
scripts/build/output-distance.py, if we also cherry-pickĀ the
first two commits we update scm/framework-ps.scm and
scripts/build/output-distance.py to be identical to the code
in master. There's no reason not to do so: The first commit
fixes pdf metadata generation, the 2nd improves debugging
output during executino of output-distance.py.
Knut
- Some cherry-picks for stable/2.20,
Knut Petersen <=