From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Upgrading Erlang and ejabberd
Date: Tue, 9 May 2017 21:42:01 +0200 [thread overview]
Message-ID: <20170509214201.7772feeb@free-electrons.com> (raw)
In-Reply-To: <CAJtjsKZU5FzxA9gidh0ZVoiQVdag6YEbWH75iDQ3XCmQ+KBC-Q@mail.gmail.com>
Hello,
On Tue, 9 May 2017 18:37:27 +0200, Johan Oudinet wrote:
> I won't have time to work on updating ejabberd this week but I can have a
> look next week.
> Feel free to upgrade erlang in the meantime even if it breaks ejabberd.
Anyway the "master" branch is closed to version bumps, so new version
bumps will go in the "next" branch. We can therefore take the erlang
bump, and merge later the ejabberd bump.
Or perhaps, we will not even have merged the erlang bump by the time
your work on bumping ejabberd.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-09 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 13:07 [Buildroot] Upgrading Erlang and ejabberd Frank Hunleth
2017-05-09 13:44 ` Peter Korsgaard
2017-05-09 15:34 ` Bernd Kuhls
2017-05-09 16:37 ` Johan Oudinet
2017-05-09 19:42 ` Thomas Petazzoni [this message]
2017-05-11 13:24 ` Frank Hunleth
2017-05-30 14:57 ` Johan Oudinet
2017-05-30 15:09 ` Frank Hunleth
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=20170509214201.7772feeb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.