unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Tomi Ollila <tomi.ollila@iki.fi>
Cc: notmuch@notmuchmail.org, David Bremner <bremner@debian.org>,
	Stefano Zacchiroli <zack@upsilon.cc>
Subject: Re: [PATCH] debian: package ruby bindings
Date: Sat, 13 Apr 2013 01:49:23 -0500	[thread overview]
Message-ID: <CAMP44s18PBYirDFsz4F3famgR6v0WTG0xgRJe=D1jWamwAXUyQ@mail.gmail.com> (raw)
In-Reply-To: <m2zjx3t0ri.fsf@guru.guru-group.fi>

On Sat, Apr 13, 2013 at 1:14 AM, Tomi Ollila <tomi.ollila@iki.fi> wrote:
> On Sat, Apr 13 2013, Felipe Contreras <felipe.contreras@gmail.com> wrote:
>
>> On Wed, Apr 3, 2013 at 5:27 PM, Felipe Contreras
>> <felipe.contreras@gmail.com> wrote:
>>> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
>>> ---
>>>  debian/control              | 14 ++++++++++++++
>>>  debian/notmuch-ruby.install |  1 +
>>>  debian/rules                |  9 +++++++++
>>>  3 files changed, 24 insertions(+)
>>>  create mode 100644 debian/notmuch-ruby.install
>>
>> No comments? Should I push this?
>
> How do we ensure that ruby package is working in every release;
> there seems to be no tests for it ?

We probably should have tests, but how is that relevant to this patch?
The code is already there, and distributions are already shipping it:

https://projects.archlinux.org/svntogit/community.git/plain/trunk/PKGBUILD?h=packages/notmuch

If there's reason to be worried about shipping something that doesn't
work, too late, we are already shipping it. And that's orthogonal to
this patch, shouldn't prevent it to be merged.

Cheers.

-- 
Felipe Contreras

  reply	other threads:[~2013-04-13  6:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 23:27 [PATCH] debian: package ruby bindings Felipe Contreras
2013-04-13  4:32 ` Felipe Contreras
2013-04-13  6:14   ` Tomi Ollila
2013-04-13  6:49     ` Felipe Contreras [this message]
2013-04-13 11:35   ` David Bremner
2013-04-13 14:49     ` Felipe Contreras
2013-04-13 15:00       ` David Bremner
2013-04-13 15:03         ` Felipe Contreras
2013-04-13 15:31           ` David Bremner
2013-04-14 13:52 ` David Bremner
2013-04-15  1:19   ` Felipe Contreras
2013-04-15 10:24     ` David Bremner
2013-04-16 18:38       ` Felipe Contreras
2013-04-15 10:34     ` David Bremner
2013-04-15 17:13       ` Felipe Contreras
2013-04-23 23:35         ` David Bremner
2013-04-24  7:20           ` Felipe Contreras
2013-04-28  7:18           ` Felipe Contreras
2013-04-29  1:22             ` David Bremner
2013-04-29  5:34               ` Felipe Contreras
2013-04-29 10:38                 ` David Bremner
2013-04-29 17:57                   ` Felipe Contreras
2013-04-29 18:16                     ` Carl Worth
2013-04-29 18:30                       ` Felipe Contreras
2017-03-12 16:11 ` 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='CAMP44s18PBYirDFsz4F3famgR6v0WTG0xgRJe=D1jWamwAXUyQ@mail.gmail.com' \
    --to=felipe.contreras@gmail.com \
    --cc=bremner@debian.org \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    --cc=zack@upsilon.cc \
    /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).