From: Sinan Akman <sinan@writeme.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-24
Date: Sat, 25 Jan 2014 16:13:52 -0500 [thread overview]
Message-ID: <52E42910.3070008@writeme.com> (raw)
In-Reply-To: <20140125073008.54D11100890@stock.ovh.net>
On 01/25/2014 02:30 AM, Thomas Petazzoni wrote:
> Build statistics for 2014-01-24
> ===============================
> [...]
Thomas, you used to have build results classified per architecture.
Do you not generate them any more ?
Thanks
sinan
next prev parent reply other threads:[~2014-01-25 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-24 Thomas Petazzoni
2014-01-25 21:13 ` Sinan Akman [this message]
2014-01-26 5:54 ` Thomas Petazzoni
2014-01-26 6:23 ` Sinan Akman
2014-01-26 6:31 ` Baruch Siach
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=52E42910.3070008@writeme.com \
--to=sinan@writeme.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.