From: rony <md.rashedul.amin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building a Linux from scratch and new target architecture
Date: Wed, 20 Jan 2016 19:34:40 -0800 (PST) [thread overview]
Message-ID: <1453347280476-123228.post@n4.nabble.com> (raw)
In-Reply-To: <CAAXf6LWcEtAe+cHpiSOCJddhW58nAdOZdLGangX+j8gGSVf7NA@mail.gmail.com>
He replied before you and subscribed when you comment. I guess that's why.
--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Building-a-Linux-from-scratch-and-new-target-architecture-tp122990p123228.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next prev parent reply other threads:[~2016-01-21 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 11:03 [Buildroot] Building a Linux from scratch and new target architecture ronyboss
2016-01-19 15:37 ` Thomas Petazzoni
2016-01-20 16:12 ` rony
2016-01-20 19:21 ` Thomas De Schampheleire
2016-01-21 3:34 ` rony [this message]
2016-01-20 14:18 ` Thomas De Schampheleire
2016-01-20 16:14 ` rony
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=1453347280476-123228.post@n4.nabble.com \
--to=md.rashedul.amin@gmail.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