All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dushara Jayasinghe <nidujay@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add package Prosody
Date: Sat, 9 Sep 2017 08:22:35 +1000	[thread overview]
Message-ID: <20170908222235.GA18631@localhost> (raw)
In-Reply-To: <1504909108-18547-2-git-send-email-nidujay@gmail.com>

So I stuffed it up...

The following was meant to go along with the email:

This is my first use of git send-email so please excuse any
stuff ups.

I'm hoping this will be a reply to 
http://lists.busybox.net/pipermail/buildroot/2017-September/201799.html

Some additional comments:

> * Do you really need Lua 5.1 specifically? Other versions of Lua, or
>   LuaJIT are not suitable ?
 
According to Zach from the prosody dev mailing list, this version of
prosody requires lua 5.1

> * The license information should be more specific than MIT/X11. Is it
>   MIT *or* X11, or a combination of both MIT code and X11 code ? If
>   so, which part is under which license ?
 
This was bit unclear, based on the COPYING file it matches the MIT 
license as specified in Wikipedia, so I'm going with that.

  reply	other threads:[~2017-09-08 22:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <[Buildroot] Add package Prosody>
2017-09-08 22:18 ` [Buildroot] [PATCH] Add package Prosody Dushara Jayasinghe
2017-09-08 22:22   ` Dushara Jayasinghe [this message]
2017-09-09 17:01   ` Yann E. MORIN
2017-09-11 11:34   ` [Buildroot] [PATCH v2] package/prosody: new package Dushara Jayasinghe
2017-09-11 11:44     ` Dushara Jayasinghe
2017-09-11 11:49   ` Dushara Jayasinghe
2017-09-13 10:45     ` Dushara Jayasinghe
2017-09-11 12:18   ` Dushara Jayasinghe
2017-09-30 21:16     ` Yann E. MORIN
2017-09-30 22:13     ` [Buildroot] [PATCH v3 1/1] " Dushara Jayasinghe
2017-10-12 21:25       ` Thomas Petazzoni

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170908222235.GA18631@localhost \
    --to=nidujay@gmail.com \
    --cc=buildroot@busybox.net \
    /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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.