From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Wael M. Nasreddine" <wael.nasreddine@gmail.com>,
guyzmo+notmuch@m0g.net, notmuch@notmuchmail.org
Subject: Re: Github?
Date: Thu, 08 May 2014 15:23:17 -0500 [thread overview]
Message-ID: <536be7b5df61a_3ce710a12ec87@nysa.notmuch> (raw)
In-Reply-To: <CA+kKtKCP8Oo2sHz5Cd0+=BmS9UK=b2h9GrGopUFwWZ=GJUXqyA@mail.gmail.com>
Wael M. Nasreddine wrote:
> Can you guys at least consider splitting contrib/ and bindings/ into
> their own repo?
It don't think that's such a good idea. One of the reasons Notmuch and
other projects like the Linux kernel have everything under one tree is
that changes in the API can be done across the board.
Sure, nowadays Notmuch has much more stable API, so that might not be
such a big deal, but changes in the API do still happen, and they do,
it's important to keep all the bindings aligned.
Maybe splitting 'contrib/' wouldn't be such a bad idea, if we mentioned
these tools in the web site, as a way of propoting them.
> It will make it easier for people to use the go bindings (for
> example) or to include the vim plugin as a submodule (or Vundle bundle).
I'm not sure about the Go bindings, but as a user of the Ruby bindings,
I find it easier for Notmuch to distribute them.
As for the vim plugin, it can already be used as a bundle:
https://github.com/felipec/notmuch-vim-ruby
--
Felipe Contreras
next prev parent reply other threads:[~2014-05-08 20:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 5:28 Github? Wael Nasreddine
2014-05-08 5:30 ` Github? Wael Nasreddine
2014-05-08 7:23 ` Github? Jani Nikula
2014-05-08 7:13 ` Github? Jani Nikula
2014-05-08 8:40 ` Github? Eric
2014-05-08 10:13 ` Github? Guyzmo
2014-05-08 19:54 ` Github? Wael Nasreddine
2014-05-08 20:14 ` Github? Wael M. Nasreddine
2014-05-08 20:23 ` Felipe Contreras [this message]
2014-05-08 20:30 ` Github? Suvayu Ali
2014-05-08 21:21 ` Github? guyzmo
2014-05-08 22:00 ` Github? Suvayu Ali
2014-05-08 22:29 ` Submodules for language bindings (was: Github?) W. Trevor King
2014-05-08 22:45 ` Suvayu Ali
2014-05-08 23:35 ` W. Trevor King
2014-05-09 11:39 ` Suvayu Ali
2014-05-09 12:40 ` Felipe Contreras
2014-05-09 12:50 ` Suvayu Ali
2014-05-09 13:09 ` Felipe Contreras
2014-05-09 2:45 ` Github? Felipe Contreras
2014-05-08 20:23 ` Github? W. Trevor King
2014-05-08 22:39 ` Github? David Bremner
2014-05-08 23:18 ` Github? Wael Nasreddine
2014-05-08 23:49 ` Github? W. Trevor King
2014-05-09 0:13 ` Github? Wael Nasreddine
2014-05-09 2:28 ` Github? W. Trevor King
2014-05-09 2:44 ` Github? Felipe Contreras
2014-05-09 2:43 ` Github? Felipe Contreras
2014-05-09 2:56 ` Github? Wael Nasreddine
2014-05-09 2:54 ` Github? Felipe Contreras
2014-05-09 3:01 ` Github? W. Trevor King
2014-05-09 3:08 ` Github? Felipe Contreras
2014-05-09 3:08 ` Github? Douglas Campos
2014-05-09 2:31 ` Github? Felipe Contreras
2014-05-08 23:30 ` Github? David Bremner
2014-05-09 12:13 ` Github? Amadeusz Żołnowski
2014-05-09 12:37 ` Github? Felipe Contreras
2014-05-10 1:21 ` Github? David Bremner
2014-05-10 5:08 ` Github? Wael M. Nasreddine
2014-05-10 7:49 ` Github? Tomi Ollila
2014-05-10 8:22 ` Github? Felipe Contreras
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=536be7b5df61a_3ce710a12ec87@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=guyzmo+notmuch@m0g.net \
--cc=notmuch@notmuchmail.org \
--cc=wael.nasreddine@gmail.com \
/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).