From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuild reproduction and generation
Date: Mon, 26 Dec 2016 15:39:35 +0100 [thread overview]
Message-ID: <20161226153935.54390a45@free-electrons.com> (raw)
In-Reply-To: <CADZ=QZ=uJ-5T+d-f5RJK3uv+paCyCCFA0ihwvSHrhTT45n1Fpw@mail.gmail.com>
Hello,
On Mon, 26 Dec 2016 22:32:37 +0800, Yu-Ting, Kao wrote:
> I have another problem and it appears many times on many autobuild issue
> IDs.
Please send the full log, i.e from the point where you start the
br-reproduce-build command. Also, again, please make sure that the
99381d37002db28566d1aba257418a38c9edee39 directory doesn't exist before
issuing the command.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-26 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 8:15 [Buildroot] Autobuild reproduction and generation Yu-Ting Kao
2016-12-26 8:21 ` Thomas Petazzoni
2016-12-26 9:07 ` Yu-Ting, Kao
2016-12-26 9:16 ` Thomas Petazzoni
2016-12-26 14:32 ` Yu-Ting, Kao
2016-12-26 14:39 ` Thomas Petazzoni [this message]
2016-12-27 1:57 ` Yu-Ting, Kao
2016-12-27 9:45 ` Thomas Petazzoni
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=20161226153935.54390a45@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