From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/uclibc: fix big oops from fb354d5f
Date: Wed, 24 Jul 2013 12:58:34 -0300 [thread overview]
Message-ID: <51EFF9AA.2050501@zacarias.com.ar> (raw)
In-Reply-To: <CAG2jQ8g37RFQ_ik4mYoBvBtdNfcZ8okcydtnnWz2CDwknhiYsg@mail.gmail.com>
On 07/24/2013 12:53 PM, Markos Chandras wrote:
> Well, mistakes can happen :)
Of course, i broke shit many times :)
Regards.
prev parent reply other threads:[~2013-07-24 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 15:02 [Buildroot] [PATCH] package/uclibc: fix big oops from fb354d5f Gustavo Zacarias
2013-07-24 15:22 ` Markos Chandras
2013-07-24 15:47 ` Gustavo Zacarias
2013-07-24 15:53 ` Markos Chandras
2013-07-24 15:58 ` Gustavo Zacarias [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=51EFF9AA.2050501@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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