Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4 v3] perl-infra enhancements (branch yem/autobuild-perl)
Date: Mon, 14 Jul 2014 13:11:23 +0200	[thread overview]
Message-ID: <20140714131123.5837d7fa@free-electrons.com> (raw)
In-Reply-To: <cover.1405256442.git.yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Sun, 13 Jul 2014 15:03:20 +0200, Yann E. MORIN wrote:

> This series enhances the pkg-erl infrastructure:
>   - add possibility for packages to pass extra environment variables
>     at configure time
>   - fix perl-net-ssleay
>   - hide perl extensions written in C when doing static build

Thanks, series applied. Indeed, the thing that was preventing Fran?ois
patches from being applied is the fact that the commit logs were way
too terse, despite me asking for better commit logs.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2014-07-14 11:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 13:03 [Buildroot] [PATCH 0/4 v3] perl-infra enhancements (branch yem/autobuild-perl) Yann E. MORIN
2014-07-13 13:03 ` [Buildroot] [PATCH 1/4 v3] infra/pkg-perl: add possibility to pass extra env at configure time Yann E. MORIN
2014-07-13 13:03 ` [Buildroot] [PATCH 2/4 v3] package/perl-net-ssleay: fix buildsystem for cross-compilation Yann E. MORIN
2014-07-13 13:03 ` [Buildroot] [PATCH 3/4 v3] package/perl-net-ssleay: not available for static link Yann E. MORIN
2014-07-13 13:03 ` [Buildroot] [PATCH 4/4 v3] package/perl-xml-libxml: " Yann E. MORIN
2014-07-14 11:11 ` 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=20140714131123.5837d7fa@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