unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH 5/5] debian/control: put elpa-notmuch in Section: lisp.
Date: Thu, 07 Dec 2017 09:23:28 -0500	[thread overview]
Message-ID: <87vahi39cv.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20171130094043.2039-6-dkg@fifthhorseman.net>

On Thu 2017-11-30 04:40:43 -0500, Daniel Kahn Gillmor wrote:
> This makes lintian stop complaining about:
>
> W: elpa-notmuch: wrong-section-according-to-package-name elpa-notmuch => lisp

I'm withdrawing this patch for consideration.  I'm convinced by
bremner's argument in https://bugs.debian.org/883772 that
language-specific sections are a bad idea!

                  --dkg

  reply	other threads:[~2017-12-07 14:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30  9:40 debian packaging cleanup Daniel Kahn Gillmor
2017-11-30  9:40 ` [PATCH 1/5] debian/control: build-depend on python3-sphinx instead of python-sphinx Daniel Kahn Gillmor
2017-11-30 14:25   ` Daniel Kahn Gillmor
2017-12-03 13:35     ` Tomi Ollila
2017-12-04 14:30       ` Daniel Kahn Gillmor
2017-12-04 20:58         ` Tomi Ollila
2017-12-04 21:12           ` Tomi Ollila
2017-12-06  1:46   ` [PATCH v2] " Daniel Kahn Gillmor
2017-12-07 12:31     ` David Bremner
2017-11-30  9:40 ` [PATCH 2/5] debian/changelog: remove trailing whitespace Daniel Kahn Gillmor
2017-11-30  9:40 ` [PATCH 3/5] debian/control: Priority: extra is deprecated Daniel Kahn Gillmor
2017-11-30  9:40 ` [PATCH 4/5] debian: bump Standards-Version to 4.1.1 Daniel Kahn Gillmor
2017-12-05  1:30   ` David Bremner
2017-12-05 17:13     ` Daniel Kahn Gillmor
2017-11-30  9:40 ` [PATCH 5/5] debian/control: put elpa-notmuch in Section: lisp Daniel Kahn Gillmor
2017-12-07 14:23   ` Daniel Kahn Gillmor [this message]
2017-11-30 12:01 ` debian packaging cleanup David Bremner
2017-11-30 14:57   ` Daniel Kahn Gillmor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vahi39cv.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).