From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org, Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: [Christian Hofstaedtler] Bug#739120: ruby-notmuch: Please update ruby binary extension install path
Date: Fri, 21 Feb 2014 21:07:03 -0400 [thread overview]
Message-ID: <87ha7sx8eg.fsf@zancas.localnet> (raw)
In-Reply-To: <87vbwfzqwt.fsf@zancas.localnet>
David Bremner <david@tethera.net> writes:
> Any comments Felipe? It's debian specific, and I assume if notmuch vim
> still runs with that change, it didn't do any harm.
>
I pushed this (and uploaded to debian)
d
prev parent reply other threads:[~2014-02-22 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 3:18 [Christian Hofstaedtler] Bug#739120: ruby-notmuch: Please update ruby binary extension install path David Bremner
2014-02-22 1:07 ` David Bremner [this message]
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=87ha7sx8eg.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=felipe.contreras@gmail.com \
--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).