unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Thomas Klausner <tk@giga.or.at>
To: Jani Nikula <jani@nikula.org>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: notmuch-0.16: realpath() compatibility issue; clang visibility problem
Date: Sat, 4 Jan 2014 13:52:26 +0100	[thread overview]
Message-ID: <20140104125225.GV27614@danbala.tuwien.ac.at> (raw)
In-Reply-To: <CAB+hUn-8eyY07y3j1N3JJLQ3qWVEVPoGWHcUVkovg34xH0ZOwQ@mail.gmail.com>

On Sat, Jan 04, 2014 at 02:35:54PM +0200, Jani Nikula wrote:
> For the visibility issue please upgrade Notmuch.

Thanks. It seems 0.17 came out a short time after I downloaded notmuch :)
I don't need the visibility patch with that version any longer.
 Thomas

  parent reply	other threads:[~2014-01-04 12:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 21:47 notmuch-0.16: realpath() compatibility issue; clang visibility problem Thomas Klausner
2014-01-04 12:35 ` Jani Nikula
2014-01-04 12:46   ` Jani Nikula
2014-01-04 12:53     ` Thomas Klausner
2014-01-04 13:06       ` Tomi Ollila
2014-01-04 13:28         ` Thomas Klausner
2014-01-04 12:52   ` Thomas Klausner [this message]
2014-01-04 13:18 ` David Bremner
2014-01-04 22:37   ` Thomas Klausner
2014-01-04 22:53     ` Jani Nikula
2014-04-08 11:26 ` David Bremner
     [not found]   ` <20140408123312.GZ5053@danbala.tuwien.ac.at>
2014-06-26 12:02     ` David Bremner
2014-06-26 12:52       ` David Bremner
2014-06-26 13:08       ` notmuch-0.18 issues [was Re: notmuch-0.16: realpath() compatibility issue; clang visibility problem] Thomas Klausner
2014-06-26 13:16         ` Tomi Ollila
2014-06-26 15:00         ` David Bremner
2017-03-12 16:21         ` David Bremner
2017-03-12 17:24           ` Tomi Ollila
2017-03-12 20:52             ` Thomas Klausner
2017-03-12 16:00 ` notmuch-0.16: realpath() compatibility issue; clang visibility problem 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=20140104125225.GV27614@danbala.tuwien.ac.at \
    --to=tk@giga.or.at \
    --cc=jani@nikula.org \
    --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).