From: Alex ter Weele <alex.ter.weele@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 39841@debbugs.gnu.org
Subject: [bug#39841] [WIP PATCH] synapse
Date: Sun, 29 Mar 2020 20:28:45 -0400 [thread overview]
Message-ID: <87pncuy9c2.fsf@librem.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87o8sfvsht.fsf@devup.no> (Marius Bakke's message of "Sun, 29 Mar 2020 22:03:10 +0200")
Marius Bakke <mbakke@fastmail.com> writes:
> Alex ter Weele <alex.ter.weele@gmail.com> writes:
>
>> Hello,
>>
>> These are some patches to add Synapse
>> <https://github.com/matrix-org/synapse>.
>
> Cool! Now Guix users can run their own Matrix home servers!
>
> Can you rebase this series on the current master branch? Let's try to
> merge the patches that are not marked with TODO, to make reviewing the
> remainder easier.
>
> I've applied the first patch already! :-)
>
> Short feedback on the series: inputs should probably be
> propagated-inputs in all of these. Please also run 'guix lint' on each
> package to catch cosmetic issues.
>
> Thanks in advance, and sorry for the delay!
Here is a new patch series atop current master. It should be
guix-linted and use propagated-inputs.
I also want to mention: I indiscriminately put everything in
python-xyz.scm, some of these packages may be a better fit for other
python-*.scm files.
Thanks for the review!
next prev parent reply other threads:[~2020-03-30 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 17:53 [bug#39841] [WIP PATCH] synapse Alex ter Weele
2020-02-29 19:12 ` Alex ter Weele
2020-02-29 19:14 ` Alex ter Weele
2020-03-28 22:22 ` Alex ter Weele
2020-03-29 20:03 ` Marius Bakke
2020-03-30 0:28 ` Alex ter Weele [this message]
2020-03-30 0:35 ` Alex ter Weele
2020-04-02 18:49 ` bug#39841: " Marius Bakke
2020-03-30 0:42 ` [bug#39841] " Alex ter Weele
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=87pncuy9c2.fsf@librem.i-did-not-set--mail-host-address--so-tickle-me \
--to=alex.ter.weele@gmail.com \
--cc=39841@debbugs.gnu.org \
--cc=mbakke@fastmail.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 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.