Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: how to select for non-volatile /var/log?
Date: Tue, 14 Feb 2017 16:49:41 +0100	[thread overview]
Message-ID: <1487087381.13854.350.camel@intel.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1702141011420.29478@uk63952.mitel.com>

On Tue, 2017-02-14 at 10:12 -0500, Robert P. J. Day wrote:
> On Tue, 14 Feb 2017, Patrick Ohly wrote:
> 
> > On Tue, 2017-02-14 at 09:31 -0500, Robert P. J. Day wrote:
> > >   i recall, once upon a time, a discussion of how to best support a
> > > non-volatile /var/log directory:
> > >
> > > https://patchwork.openembedded.org/patch/90151/
> >
> > A more recent, but also still unmerged patch for this functionality
> > is here: https://patchwork.openembedded.org/patch/90839/
> 
>   "more recent" would appear to be a relative term, since the date on
> that is may of 2015.

It was reposted late last year, I just didn't pick the more recent entry
in patchwork. Here's the current one:
https://patchwork.openembedded.org/series/4028/

> it seems that this topic comes up every so often,
> then just dies. so is there any *current* discussion to add this
> feature? be nice if this issue was just resolved, one way or the
> other.

Fully agreed.

-- 
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.





      reply	other threads:[~2017-02-14 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 14:31 how to select for non-volatile /var/log? Robert P. J. Day
2017-02-14 14:51 ` Patrick Ohly
2017-02-14 15:12   ` Robert P. J. Day
2017-02-14 15:49     ` Patrick Ohly [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=1487087381.13854.350.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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