From: Saul Wold <sgw@linux.intel.com>
To: Ben Shelton <ben.shelton@ni.com>, Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Richard Tollerton : bootlogd: ensure /var/log/boot is created in volatiles
Date: Tue, 22 Jul 2014 08:38:54 -0700 [thread overview]
Message-ID: <53CE858E.9080706@linux.intel.com> (raw)
In-Reply-To: <20140722153012.GA30289@bshelton-desktop>
On 07/22/2014 08:30 AM, Ben Shelton wrote:
> On 07/22, Martin Jansa wrote:
>> On Mon, Jul 21, 2014 at 06:25:15PM +0000, git@git.openembedded.org wrote:
>>> Module: openembedded-core.git
>>> Branch: master-next
>>> Commit: 6f963d761fa2916711b0d7808351515383bd5298
>>> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=6f963d761fa2916711b0d7808351515383bd5298
>>>
>>> Author: Richard Tollerton <rich.tollerton@ni.com>
>>> Date: Mon Jul 21 10:50:56 2014 -0500
>>>
>>> bootlogd: ensure /var/log/boot is created in volatiles
>>
>> subject usually starts with recipe/bbclass name, so it should be
>> sysvinit not bootlogd.
>>
>>
>> Please don't mix tabs and spaces for indentation, only spaces should be used
>> in multi-line variables.
>>
>
> Sorry about that -- do we need to resubmit the patch, or has it already
> been merged?
>
It has not been merged yet, so please resubmit a v2 with fixed white space.
Sau!
> Thanks,
> Ben
>
>>
>> --
>> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
>
>
prev parent reply other threads:[~2014-07-22 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140721182515.CD7355015A@opal.openembedded.org>
2014-07-22 9:18 ` [oe-commits] Richard Tollerton : bootlogd: ensure /var/log/boot is created in volatiles Martin Jansa
2014-07-22 15:30 ` Ben Shelton
2014-07-22 15:38 ` Saul Wold [this message]
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=53CE858E.9080706@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=ben.shelton@ni.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox