unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] test: use gpgconf --create-socketdir if available
Date: Wed, 15 Feb 2017 13:59:31 -0500	[thread overview]
Message-ID: <8737ffjn58.fsf@rocinante.cs.unb.ca> (raw)
In-Reply-To: <87efyzl3n8.fsf@alice.fifthhorseman.net>

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

> I'd love to not see this kind of workaround cruft pile up, because it
> tends to cause problems in the future.  is there a way that we can mark
> this sort of thing for fairly prompt removal once it's fixed upstream?

Maybe once a gnupg bug is filed, write to this list with the suggestion
that we back out the workaround when the bug is fixed upstream
(although we have to think about how long to support gnupg
2.1.18. Thanks debian!). We can then tag that message as a bug in
nmbug.

d

  reply	other threads:[~2017-02-15 18:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 21:42 Proposed fix for test failures due to long socket paths David Bremner
2017-02-14 21:42 ` [PATCH 1/2] configure: add test for gpgconf --create-socketdir David Bremner
2017-02-14 22:02   ` David Bremner
2017-02-14 21:42 ` [PATCH 2/2] test: use gpgconf --create-socketdir if available David Bremner
2017-02-15 18:17   ` Daniel Kahn Gillmor
2017-02-15 18:59     ` David Bremner [this message]
2017-02-19 10:24   ` Tomi Ollila
2017-02-21 12:19 ` Proposed fix for test failures due to long socket paths David Bremner

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=8737ffjn58.fsf@rocinante.cs.unb.ca \
    --to=david@tethera.net \
    --cc=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).