| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 00-build.patch | Adjustments to the ant build.xml file. Mainly to use system-provided JARs and not depend on Internet connection. Also adds support to build the translations in the i18n directory. The Debian package build is identified using the Build-Name in the REVISION file and is not considered local build. |
Bas Couwenberg <sebastic@debian.org> | not-needed | |||
| 01-bts.patch | Include Debian version number and BTS link. Bugs for the JOSM version present in Debian have to be filed in Debian's BTS and not upstream. Also include the Debian version number for better bug triaging. |
Andreas Putzo <andreas@putzo.net> | not-needed | |||
| 05-fix_version.patch | Fix version numbers to reflect upstream changes. Appending SVN to version is not required for the Debian package build. The Debian package build is identified using the Build-Name property in the REVISION file (see 00-build.patch). |
Mario Izquierdo <mariodebian@gmail.com> | not-needed | debian | ||
| 06-move_data_out_of_jar.patch | Move sharable data out of josm.jar. | Paul Hartmann <phaaurlt@googlemail.com> | not-needed | debian | ||
| 07-use_system_fonts.patch | Use system Noto fonts, instead of the embedded Droid fonts. | Bas Couwenberg <sebastic@debian.org> | not-needed | |||
| 08-use_noto_font.patch | Use Noto font instead of Droid. | Bas Couwenberg <sebastic@debian.org> | yes | debian | ||
| svn-r19214.patch | Fix #23908: Significantly improve the performance of copy/paste when dealing with large amounts of data From #23908, at least one valid workflow involves copy/pasting large amounts of data (specifically updating boundaries). The relation for Terwolde in the sample data had 2206 objects. This took >5 minutes to copy between layers. With this change, it takes <1 second. . This is a performance regression from r19176. The primary culprit from r19176 is when we check the size of the dataset. The problem is that we check to see if the size of the primitives being changed is greater than or equal to the non-deleted complete primitives in the dataset. We get a new filtered collection each time we get those primitives, and therefore the size of that is not cached. The size calculation for the filtered collection is where almost all the expense is. We fix that by wrapping the work from AddPrimitivesCommand in DataSet#update to have a single large update at the end of the copy operation. This ensures that we do not have many spurious fired event calls when a mass operation is going on. |
Taylor Smock | yes | upstream | https://josm.openstreetmap.de/changeset/19214/josm |