Package: sponsorship-requests Severity: wishlist Control: block -1 by 861705
Dear mentors, I am looking for a sponsor for my package "writeroom-mode" * Package name : writeroom-mode Version : 3.6.1-1 Upstream Author : Joost Kremers <joostkrem...@fastmail.fm> * URL : https://github.com/joostkremers/writeroom-mode * License : BSD-3-clause Section : lisp It will be maintained in the pkg-emacsen project: ssh://git.debian.org/git/pkg-emacsen/pkg/writeroom-mode.git It builds this binary package: elpa-writeroom-mode - Minor mode for distraction-free writing To access further information about this package, please visit the following URL: https://mentors.debian.net/package/writeroom-mode Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/w/writeroom-mode/writeroom-mode_3.6.1-1.dsc And here is changelog: writeroom-mode (3.6.1-1) unstable; urgency=medium * Initial release. (Closes: #861124) * Add 0001-Use-Texinfo-format-for-directory-declaration-for-inf.patch and 0002-Fix-menu-entry-in-texi-before-body.patch and 0003-Increase-header-levels-of-customisation-options-in-R.patch - These are needed to fix a variety of issues with the info file, including the lintian error "info-document-missing-dir-entry". -- Nicholas D Steeves <nstee...@gmail.com> Wed, 03 May 2017 15:52:36 -0400 Do the headers for the patches I cherry-picked (one manual 3-way merge) from upstream look ok? Specifically I'm wondering if I should use the "Applied-Upstream: commit hash" or "Applied-Upstream: commit: hash". I chose the former. Cheers, Nicholas
signature.asc
Description: Digital signature
