From: "J. Lewis Muir" <jlmuir@imca-cat.org>
To: Bart Bunting <bart.bunting@ursys.com.au>, notmuch@notmuchmail.org
Subject: Re: muchsync and osx compile failure
Date: Mon, 9 Nov 2015 10:35:30 -0600 [thread overview]
Message-ID: <5640CB52.8000102@imca-cat.org> (raw)
In-Reply-To: <m2ziyoq776.fsf@ursys.com.au>
On 11/8/15 7:42 PM, Bart Bunting wrote:
> Hi,
>
> Not sure if it is appropriate to post to this list with muchsync
> questions but if not could someone let me know...
Hi, Bart.
I would say you should do what it says in the Contact section at the
bottom of the Muchsync website[1]:
Please email questions, comments, testimonials, bug reports, patches,
and pull requests to the author (preferably with the word "muchsync"
in the email subject).
Regards,
Lewis
[1] http://www.muchsync.org/
prev parent reply other threads:[~2015-11-09 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 1:42 muchsync and osx compile failure Bart Bunting
2015-11-09 16:35 ` J. Lewis Muir [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=5640CB52.8000102@imca-cat.org \
--to=jlmuir@imca-cat.org \
--cc=bart.bunting@ursys.com.au \
--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).