From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Make libmicrohttpd version configurable
Date: Tue, 6 Mar 2012 18:20:46 +0100 [thread overview]
Message-ID: <20120306182046.56f21098@skate> (raw)
In-Reply-To: <1331054328-6564-1-git-send-email-rolandu@gmail.com>
Le Tue, 6 Mar 2012 19:18:48 +0200,
rolandu at gmail.com a ?crit :
> From: Roland Uuesoo <roland@martem.eu>
Except for some particular packages such as U-Boot or the kernel, which
are highly hardware-dependent, we generally don't like having multiple
version support for userspace libraries/applications.
Could you give us details as to why this would be needed specifically
for libmicrohttpd?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-03-06 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 17:18 [Buildroot] [PATCH] Make libmicrohttpd version configurable rolandu at gmail.com
2012-03-06 17:20 ` Thomas Petazzoni [this message]
[not found] ` <CAG0mjpva6VP1u7EK9oOXUqeYYypCiC2yuE7ag4UtBqCkgc52UA@mail.gmail.com>
2012-03-06 17:49 ` Thomas Petazzoni
2012-03-06 18:14 ` Roland
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=20120306182046.56f21098@skate \
--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.