From: Markos Chandras <Markos.Chandras@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/trinity: New package
Date: Wed, 8 Oct 2014 15:57:42 +0100 [thread overview]
Message-ID: <543550E6.9070501@imgtec.com> (raw)
In-Reply-To: <54355087.3090108@imgtec.com>
On 10/08/2014 03:56 PM, Vicente Olivert Riera wrote:
> Dear Waldemar Brodkorb,
>
> On 10/08/2014 03:53 PM, Waldemar Brodkorb wrote:
>> Hi,
>>
>> may be I missed it in v1, is there a reason for
>> depends on !BR2_TOOLCHAIN_USES_UCLIBC ?
>
> This is the v1 patch. You can see the reason there.
>
Still it's probably a good idea to have a comment in Config.in
since neither Config.in nor commit message explain the reason so one may
forget and remove the restriction in the future.
--
markos
next prev parent reply other threads:[~2014-10-08 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 10:22 [Buildroot] [PATCH v2] package/trinity: New package Vicente Olivert Riera
2014-10-08 14:53 ` Waldemar Brodkorb
2014-10-08 14:56 ` Vicente Olivert Riera
2014-10-08 14:57 ` Vicente Olivert Riera
2014-10-08 14:57 ` Markos Chandras [this message]
2014-10-08 15:14 ` Vicente Olivert Riera
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=543550E6.9070501@imgtec.com \
--to=markos.chandras@imgtec.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