Sign me up Login

Details about package markdown-mode

Name: markdown-mode (PTS)
Uploader: Xiyue Deng <manphiz@gmail.com> (Debian QA page)
Description: elpa-markdown-mode - mode for editing Markdown-formatted text files in GNU Emacs

Package uploads

Upload #1

Information

Version: 2.6-3
Uploaded: 2024-07-28 08:09
Source package: markdown-mode_2.6-3.dsc
Distribution: unstable
Section: lisp
Priority: optional
Homepage: https://jblevins.org/projects/markdown-mode/
Vcs-Git: https://salsa.debian.org/emacsen-team/markdown-mode.git
Vcs-Browser: https://salsa.debian.org/emacsen-team/markdown-mode
Closes bugs: #1073099

Changelog

 markdown-mode (2.6-3) unstable; urgency=medium
 .
   [ Xiyue Deng ]
   * Fix ERT test by ensuring correct build directory in d/ert-helper.el
   * Drop patches disabling tests now that they all pass
   * Drop unused override_dh_auto_test in d/rules (dh_elpa_test is in
     effect)
   * Update Standards-Version to 4.7.0; no change needed
   * Update debian copyright holders and years based on git history in
     d/copyright
 .
   [ Nicholas D Steeves and Xiyue Deng ]
   * Discount has provided a Markdown 1.0-compatible interface to users of this
     package since 2.3+290-1.  Given four years of testing by a subset of
     users, and given the pending removal of the original markdown package, it
     is finally time to:
     - Migrate to discount by default for packages builds (Closes: #1073099)
 .
     TODO: read the source code to see if it needs to be patched to use
     discount-by-default during tests, as well as in the default config.  That
     work will go in this section.  Answer if they're unit tests or functional
     tests?  That justification needs to go here.  If I have to look this
     stuff up myself then you can't share credit.
 .
     P.S: Were we to "discount | libtext-multimarkdown-perl", the latter would
     never be tested, because the first branch is always chosen.
 .
     - Drop markdown from Recommends
 .
   [ Nicholas D Steeves ]
   * Update my copyright date range.

QA information

Comments

No comments