From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request v2] Pull request for branch yem/patchwork
Date: Thu, 14 Nov 2013 19:46:55 +0100 [thread overview]
Message-ID: <cover.1384454667.git.yann.morin.1998@free.fr> (raw)
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
Hello All!
This series ensures that taregt/ and our copy of busybox .config are
writeable.
In case the Buildroot tree is RO (eg. shared via a read-only NFS mount),
target/ would end-up read-only, which is a bit awkward, since we won't be
able to add files in there. Ditto for the busybox' .config file, since we
need to tweak it with sed.
I've had this locally for some time now, grabbed from some patches in
patchwork. A previous submission of this series has been marked as
"Changes Requested", but there's no trace of it in the ML, so I'm just
re-spinning them as-is for further comments.
Changes v1 -> v2:
- add three other files to the list (Danomi)
Regards,
Yann E. MORIN.
Regards,
Yann E. MORIN.
The following changes since commit 2b9bdcafa3d69bcc3d63d5d1d3d2ab692413b39d:
qemu/arm-nuri: bump to latest 3.10.x kernel version (2013-11-14 12:25:04 +0100)
are available in the git repository at:
git://gitorious.org/buildroot/buildroot.git yem/patchwork
for you to fetch changes up to 9bc9c11ace25603f32efc9248e9a513581192f59:
fs: ensure $(TARGET_DIR_WARNING_FILE) is writable (2013-11-14 19:41:09 +0100)
----------------------------------------------------------------
Nathan Lynch (2):
target: ensure target/ dir is writable
busybox: ensure $(BUSYBOX_BUILD_CONFIG) is writable
Yann E. MORIN (3):
linux: ensure buildroot_defconfig is writable
package/uClibc: ensure .oldconfig is writable
fs: ensure $(TARGET_DIR_WARNING_FILE) is writable
Makefile | 6 +++---
fs/common.mk | 2 +-
linux/linux.mk | 2 +-
package/busybox/busybox.mk | 2 +-
package/uclibc/uclibc.mk | 2 +-
5 files changed, 7 insertions(+), 7 deletions(-)
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next reply other threads:[~2013-11-14 18:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 18:46 Yann E. MORIN [this message]
2013-11-14 18:46 ` [Buildroot] [PATCH 1/5] target: ensure target/ dir is writable Yann E. MORIN
2014-01-28 0:31 ` Danomi Manchego
2014-01-28 18:25 ` Yann E. MORIN
2014-01-28 18:37 ` Danomi Manchego
2013-11-14 18:46 ` [Buildroot] [PATCH 2/5] busybox: ensure $(BUSYBOX_BUILD_CONFIG) " Yann E. MORIN
2013-11-14 18:46 ` [Buildroot] [PATCH 3/5] linux: ensure buildroot_defconfig " Yann E. MORIN
2013-11-14 19:24 ` Danomi Manchego
2013-11-14 18:46 ` [Buildroot] [PATCH 4/5] package/uClibc: ensure .oldconfig " Yann E. MORIN
2013-11-15 8:18 ` Thomas Petazzoni
2013-11-14 18:46 ` [Buildroot] [PATCH 5/5] fs: ensure $(TARGET_DIR_WARNING_FILE) " Yann E. MORIN
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=cover.1384454667.git.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--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