From: Patrick Ohly <patrick.ohly@intel.com>
To: "Ulrich Ölmann" <u.oelmann@pengutronix.de>,
"Eduard Bartosh" <eduard.bartosh@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Contents of non-rootfs partitions
Date: Thu, 24 Nov 2016 08:38:02 +0100 [thread overview]
Message-ID: <1479973082.6873.8.camel@intel.com> (raw)
In-Reply-To: <20161124061543.e2xpgh7zjir3oynk@pengutronix.de>
On Thu, 2016-11-24 at 07:15 +0100, Ulrich Ölmann wrote:
> On Wed, Nov 23, 2016 at 04:56:56PM +0100, Patrick Ohly wrote:
> > Excluding only the directory content but not the actual directory is
> > indeed a good point. I'm a bit undecided. When excluding only the
> > directory content, there's no way of building a rootfs without that
> > mount point, if that's desired. OTOH, when excluding also the directory,
> > the data would have to be staged under a different path in the rootfs
> > and the mount point would have to be a separate, empty directory.
> >
> > I'm leaning towards excluding the directory content and keeping the
> > directory.
>
> what about having both possibilities by leaning against the syntax that rsync
> uses to specify if a whole source directory or only it's contents shall be
> synced to some destination site (see [1])?
I like that idea.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2016-11-24 7:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 9:05 Contents of non-rootfs partitions Kristian Amlie
[not found] ` <CA+4=imZLMh7di712mejxQ6qgsDSXiCOJJDbUY99YC9DoCrqrmQ@mail.gmail.com>
2016-11-22 9:54 ` Kristian Amlie
2016-11-22 11:10 ` Patrick Ohly
2016-11-22 11:54 ` Kristian Amlie
2016-11-23 8:40 ` Enrico Joerns
2016-11-23 9:04 ` Kristian Amlie
2016-11-23 9:24 ` Maciej Borzęcki
2016-11-23 10:12 ` Enrico Joerns
2016-11-23 11:03 ` Maciej Borzęcki
2016-11-23 12:08 ` Ed Bartosh
2016-11-23 13:08 ` Kristian Amlie
2016-11-23 13:22 ` Ed Bartosh
2016-11-23 13:51 ` Maciej Borzęcki
2016-11-23 14:10 ` Ed Bartosh
2016-11-23 15:56 ` Patrick Ohly
2016-11-24 6:15 ` Ulrich Ölmann
2016-11-24 7:38 ` Patrick Ohly [this message]
2016-11-24 7:38 ` Kristian Amlie
2016-11-24 13:23 ` Ed Bartosh
2016-11-24 14:43 ` Kristian Amlie
2016-11-24 14:51 ` Ed Bartosh
2016-11-24 15:24 ` Patrick Ohly
2016-11-24 15:52 ` Kristian Amlie
2016-11-24 15:28 ` Andreas Oberritter
2016-11-24 15:51 ` Kristian Amlie
2016-11-24 16:21 ` Patrick Ohly
2016-11-24 16:40 ` Kristian Amlie
2016-11-23 13:44 ` Ed Bartosh
2016-11-23 14:20 ` Kristian Amlie
2016-11-22 23:45 ` Khem Raj
2016-11-23 7:13 ` Kristian Amlie
2016-11-23 7:26 ` Khem Raj
2016-11-23 9:01 ` Kristian Amlie
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=1479973082.6873.8.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=eduard.bartosh@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=u.oelmann@pengutronix.de \
/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.