From: Jason Wessel <jason.wessel@windriver.com>
To: Phil Blundell <pb@pbcl.net>
Cc: Openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 2/6] unfs3, unfs-server: Replace all instances of unfs-server with unfs3
Date: Thu, 23 Jan 2014 09:35:13 -0600 [thread overview]
Message-ID: <52E136B1.5020805@windriver.com> (raw)
In-Reply-To: <1390489330.24755.17.camel@e130.pbcl.net>
On 01/23/2014 09:02 AM, Phil Blundell wrote:
> On Thu, 2014-01-23 at 08:32 -0600, Jason Wessel wrote:
>> # Not automake, no out of tree build support
>> -#B_pn-unfs-server-native = "${SEPB}"
>> +#B_pn-unfs3-native = "${SEPB}"
> Is that still true? The unfs3 recipe makes it look like it does use
> autotools.
With v1 no, with v2 yes. I had done a global search and replace. I would say we can dump these commented out lines.
Thanks,
Jason.
next prev parent reply other threads:[~2014-01-23 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 14:32 [PATCH v2 0/6] Replace unfs-server with unfs3 Jason Wessel
2014-01-23 14:32 ` [PATCH v2 1/6] unfs3: Add a NFSv3 user mode server for use with runqemu Jason Wessel
2014-01-23 15:01 ` Phil Blundell
2014-01-23 16:52 ` Jason Wessel
2014-02-01 9:22 ` Richard Purdie
2014-02-01 14:00 ` Jason Wessel
2014-01-23 14:32 ` [PATCH v2 2/6] unfs3, unfs-server: Replace all instances of unfs-server with unfs3 Jason Wessel
2014-01-23 15:02 ` Phil Blundell
2014-01-23 15:35 ` Jason Wessel [this message]
2014-01-23 14:32 ` [PATCH v2 3/6] runqemu: Use the newer unfs3 for serving user space nfs Jason Wessel
2014-01-23 14:32 ` [PATCH v2 4/6] unfs-server: Remove unfs-server recipe and patches Jason Wessel
2014-01-23 14:32 ` [PATCH v2 5/6] runqemu-export-rootfs: update for unfs3 Jason Wessel
2014-01-23 14:32 ` [PATCH v2 6/6] runqemu, runqemu-internal: Allow slirp for NFS and KVM use Jason Wessel
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=52E136B1.5020805@windriver.com \
--to=jason.wessel@windriver.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.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