From: Leo Famulari <leo@famulari.name>
To: "Clément Lassieur" <clement.lassieur@parrot.com>
Cc: guix-devel@gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: Re: [PATCH] gnu: Add prosody service
Date: Sat, 26 Nov 2016 18:41:58 -0500 [thread overview]
Message-ID: <20161126234158.GA24470@jasmine> (raw)
In-Reply-To: <20161126172012.1085-1-clement.lassieur@parrot.com>
On Sat, Nov 26, 2016 at 06:20:12PM +0100, Clément Lassieur wrote:
> From: Clément Lassieur <clement@lassieur.org>
Hi, thanks for working on this!
>
> ---
> gnu/local.mk | 1 +
> gnu/packages/messaging.scm | 3 +
> gnu/services/messaging.scm | 787 +++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 791 insertions(+)
> create mode 100644 gnu/services/messaging.scm
Which version of the patch should we review? :)
If you are using `git format-patch` or `git send-email`, you can use
--subject-prefix to version your patches.
For example:
$ git send-email --cover-letter -n --thread=shallow --subject-prefix=v2 master
next prev parent reply other threads:[~2016-11-26 23:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 17:15 RFH: Add prosody service Clément Lassieur
2016-11-26 17:20 ` [PATCH] gnu: " Clément Lassieur
2016-11-26 23:41 ` Leo Famulari [this message]
2016-11-27 10:04 ` Clément Lassieur
2016-11-26 17:20 ` Clément Lassieur
2016-11-26 21:28 ` Clément Lassieur
2016-11-26 21:30 ` Clément Lassieur
2016-11-28 19:54 ` RFH: " Hartmut Goebel
2016-11-28 21:01 ` Ludovic Courtès
2016-12-02 11:19 ` Clément Lassieur
2016-12-04 21:11 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2017-01-04 21:55 [PATCH] gnu: Add Prosody service Clément Lassieur
2017-01-05 10:34 ` Hartmut Goebel
2017-01-05 10:50 ` ng0
2017-01-07 22:10 ` Clément Lassieur
2017-01-07 21:14 ` Clément Lassieur
2017-01-07 21:29 ` Ludovic Courtès
2017-01-08 19:06 ` Clément Lassieur
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=20161126234158.GA24470@jasmine \
--to=leo@famulari.name \
--cc=clement.lassieur@parrot.com \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.