From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] package/mono: bump to version 4.2.1.102
Date: Fri, 27 Nov 2015 16:09:04 +0100 [thread overview]
Message-ID: <20151127160904.00f5ea76@free-electrons.com> (raw)
In-Reply-To: <1448405513-20741-1-git-send-email-angelo.compagnucci@gmail.com>
Angelo,
On Tue, 24 Nov 2015 23:51:51 +0100, Angelo Compagnucci wrote:
> This patch series bumps mono to version 4.2.1.102
>
> Angelo Compagnucci (2):
> package/mono: bump to version 4.2.1.102
> package/monolite: bump to version 138
Applied to next, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-11-27 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 22:51 [Buildroot] [PATCH 0/2] package/mono: bump to version 4.2.1.102 Angelo Compagnucci
2015-11-24 22:51 ` [Buildroot] [PATCH 1/2] " Angelo Compagnucci
2015-11-24 22:51 ` [Buildroot] [PATCH 2/2] package/monolite: bump to version 138 Angelo Compagnucci
2015-11-27 15:09 ` Thomas Petazzoni [this message]
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=20151127160904.00f5ea76@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox