From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6866] New: Ambiguous recommend method for customizing the generated target filesystem in Manual
Date: Sun, 9 Feb 2014 19:00:51 +0000 (UTC) [thread overview]
Message-ID: <bug-6866-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6866
Summary: Ambiguous recommend method for customizing the
generated target filesystem in Manual
Product: buildroot
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: trivial
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: jeffball55 at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5234
--> https://bugs.busybox.net/attachment.cgi?id=5234
Rewords the two ambiguous sections to clarify.
The way I read Section 3.3.1 of the Manual (Customizing the generated target
filesystem) is ambiguous toward the recommended method. In my interpretation,
the section recommends both a filesystem overlay (in bullet 2) and a post-build
script (in bullet 4).
I've attached a short patch that I think clarifies this.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-02-09 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 19:00 bugzilla at busybox.net [this message]
2014-02-09 19:02 ` [Buildroot] [Bug 6866] Ambiguous recommended method for customizing the generated target filesystem in Manual bugzilla at busybox.net
2014-02-09 19:10 ` bugzilla at busybox.net
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=bug-6866-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.