Bug#1024684: dxf2gcode: Restructure debian/patches/ according to upstream status?

[Petter Reinholdtsen]

Package: dxf2gcode
Version: 20170925-4
Severity: wishlist

A fairly common way to structure the files in debian/patches/ is to
place a README file there with the following content

  0xxx: Grabbed from upstream development.
  1xxx: Possibly relevant for upstream adoption.
  2xxx: Only relevant for official Debian release.

and then use this name structure on the individual patches.  It make it
trivial to see which files are yet to be sent upstream and which one
that are most likely going away in the next version update.

Please consider using this structure for the set of patches in
debian/patches/ already:

0001-install-AppStream-metadata-in-the-correct-directory.patch
0003-create-top-level-dxf2gcode-module-move-all-modules-t.patch
0004-update-all-imports-to-use-the-new-dxf2gcode-top-leve.patch
0005-update-dxf2gcode.ui-for-new-top-level-module.patch
0006-update-egg-info-for-top-level-dxf2gcode-module.patch
0007-update-make_tr.py-for-new-top-level-module.patch
0008-update-st-setup-for-new-top-level-module.patch
0009-fix-dxf-LWPolyLine-import.patch
0010-fix-dxf-PolyLine-import.patch
0011-fix-import-of-DXF-with-no-Entities.patch
no-lupdate.patch

Perhaps some of these should be sent upstream too?

-- 
Happy hacking
Petter Reinholdtsen