From: kevin.strasser@linux.intel.com
To: "Paul Eggleton" <paul.eggleton@linux.intel.com>
Cc: kevstras@gmail.com, yocto@yoctoproject.org
Subject: Re: [meta-baryon] [PATCH 0/5] Updates and fixes
Date: Wed, 20 Mar 2013 17:42:19 -0700 (PDT) [thread overview]
Message-ID: <53276.10.24.2.83.1363826539.squirrel@linux.intel.com> (raw)
In-Reply-To: <1558587.S9v9mAN4hA@helios>
> Hi Kevin,
>
> On Monday 18 March 2013 18:05:21 Kevin Strasser wrote:
>> Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
>>
>> The following changes since commit
>> 566cb211cee8a9870257a4ac2fc706990a70b9d2:
>>
>> nfs-utils: update bbappend version to 1.2.7 (2013-02-27 15:24:30
>> +0000)
>>
>> are available in the git repository at:
>>
>> git://git.yoctoproject.org/poky-contrib strassek/baryon
>> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=strassek/baryon
>>
>> Kevin Strasser (5):
>> kernel: enable nfsd in linux-yocto 3.8
>> ffmpegthumbnailer: update to 2.0.8
>> ffmpegthumbnailer: include cstring
>> samba: sync with meta-oe
>> lvm2: sync with meta-oe
>>
>
> Looks good, thanks. My only concern is with the samba update - without
> testing
> it, it looks a bit like it won't be configured to work out of the box.
> Perhaps
> we can get away with this though given that it can be configured through
> Webmin. What do you think?
>
Sorry for the delayed response. Now that you mention it, yes it does make
sense to try to keep the old behavior when possible. It looks like we've
been keeping a custom config file to achieve that end. I'll take a closer
look and then send out a revised patch.
-Kevin
next prev parent reply other threads:[~2013-03-21 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 1:05 [meta-baryon] [PATCH 0/5] Updates and fixes Kevin Strasser
2013-03-19 10:10 ` Paul Eggleton
2013-03-21 0:42 ` kevin.strasser [this message]
2013-03-21 20:24 ` [meta-baryon] [PATCH v2 0/6] " Kevin Strasser
2013-03-25 11:49 ` Paul Eggleton
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=53276.10.24.2.83.1363826539.squirrel@linux.intel.com \
--to=kevin.strasser@linux.intel.com \
--cc=kevstras@gmail.com \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.org \
/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.