All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: yocto@yoctoproject.org
Subject: Re: update mechanisms
Date: Tue, 13 Dec 2016 10:08:35 +0100	[thread overview]
Message-ID: <1481620115.17535.262.camel@intel.com> (raw)
In-Reply-To: <ad99fb40-4d8e-c7e0-3fe8-d27bc593f8fb@topic.nl>

On Tue, 2016-12-13 at 09:51 +0100, Mike Looijmans wrote:
> On 09-12-16 16:13, Patrick Ohly wrote:
> > Hello everyone!
> >
> > Thanks for contributing directly to the page. It's great to see this
> > done collaboratively.
> 
> Nice informative page.
> 
> Only thing lacking is simple, OE-built in upgrade procedures like: "Just run 
> 'opkg update && opkg upgrade'"

Want to add it? :-)

Seriously, it would be a good addition.

-- 
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:[~2016-12-13  9:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 12:03 [meta-swupd][PATCH] bsdiff: update to latest version André Draszik
2016-11-30 11:04 ` Patrick Ohly
2016-11-30 14:31   ` André Draszik
2016-11-30 14:59     ` update mechanisms (was: Re: [meta-swupd][PATCH] bsdiff: update to latest version) Patrick Ohly
2016-11-30 17:19       ` André Draszik
2016-12-01  7:42         ` Patrick Ohly
2016-12-01 10:26           ` André Draszik
2016-12-01 11:25             ` Patrick Ohly
2016-12-06  9:01       ` update mechanisms Stefano Babic
2016-12-06  9:45         ` Patrick Ohly
2016-12-06 14:11           ` Lopez, Mariano
2016-12-06 18:45             ` Philip Balister
2016-12-06 22:38               ` Stefano Babic
2016-12-07  7:05                 ` Kristian Amlie
2016-12-09 15:13                 ` Patrick Ohly
2016-12-09 16:03                   ` Stefano Babic
2016-12-12 14:59                     ` Mariano Lopez
2016-12-12 15:41                       ` Patrick Ohly
2016-12-12 15:49                         ` Mariano Lopez
2016-12-12 19:02                           ` Patrick Ohly
2016-12-13 14:03                             ` Lopez, Mariano
2016-12-12  6:39                   ` Kristian Amlie
2017-03-02  0:35                     ` Eystein Måløy Stenberg
2017-03-10 13:02                       ` Patrick Ohly
2017-03-10 13:35                         ` Kristian Amlie
2017-03-10 14:20                           ` Patrick Ohly
2016-12-13  8:51                   ` Mike Looijmans
2016-12-13  9:08                     ` Patrick Ohly [this message]
2016-12-12 15:13           ` André Draszik
2016-12-12 15:32             ` Patrick Ohly

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=1481620115.17535.262.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=mike.looijmans@topic.nl \
    --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.