From: David VomLehn <vomlehn@texas.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] Add the capability to create sub-filesystems from the target filesystem.
Date: Thu, 29 May 2014 12:08:34 -0700 [thread overview]
Message-ID: <538785B2.2060807@texas.net> (raw)
In-Reply-To: <2385189.JHtluQLb2I@sagittea>
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140529/25c57a76/attachment.html>
next prev parent reply other threads:[~2014-05-29 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 5:24 [Buildroot] [PATCH 0/3] Manage big root directory trees by breaking them up vomlehn at canopus-us.com
2014-05-29 5:24 ` [Buildroot] [PATCH 1/3] Add the capability to create sub-filesystems from the target filesystem vomlehn at canopus-us.com
2014-05-29 9:21 ` Jérôme Pouiller
2014-05-29 19:08 ` David VomLehn [this message]
2014-05-29 5:24 ` [Buildroot] [PATCH 2/3] Allow specification of values for --prefix and --exec-prefix in autotools vomlehn at canopus-us.com
2014-05-29 5:24 ` [Buildroot] [PATCH 3/3] Support installation of Python in a different directory vomlehn at canopus-us.com
2014-05-29 9:56 ` Thomas Petazzoni
2014-10-11 14:49 ` [Buildroot] [PATCH 0/3] Manage big root directory trees by breaking them up Arnout Vandecappelle
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=538785B2.2060807@texas.net \
--to=vomlehn@texas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox