public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: aidecoe@gentoo.org
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Help maintaining dev-erlang and ejabberd
Date: Tue, 22 Aug 2017 21:50:56 +0100	[thread overview]
Message-ID: <87r2w3xr67.fsf@freja.aidecoe.name> (raw)

[-- Attachment #1: Type: text/plain, Size: 409 bytes --]

Hi,

Some time ago I've made an effort to split ejabberd into proper
dependencies handled by portage rather than repackaging bundle produced
by rebar.  While I've found that easier to maintain, my lack of
knowledge about Erlang makes maintenanace quite difficult. I'd
appreciate if someone who actually has some experience in Erlang helps
maintaining it.

Kind regards,

-- 
Amadeusz Żołnowski

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 980 bytes --]

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 20:50 aidecoe [this message]
2017-08-23  2:46 ` [gentoo-dev] Help maintaining dev-erlang and ejabberd R0b0t1
2017-08-24  2:33   ` [gentoo-dev] " Duncan
2017-08-24  4:26     ` R0b0t1
2017-08-24 21:48       ` Amadeusz Żołnowski

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=87r2w3xr67.fsf@freja.aidecoe.name \
    --to=aidecoe@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox