From: Patrick Ohly <patrick.ohly@intel.com>
To: Stefano Babic <sbabic@denx.de>
Cc: "André Draszik" <git@andred.net>,
"Lopez, Mariano" <mariano.lopez@intel.com>,
yocto@yoctoproject.org
Subject: Re: update mechanisms
Date: Tue, 06 Dec 2016 10:45:22 +0100 [thread overview]
Message-ID: <1481017522.17535.38.camel@intel.com> (raw)
In-Reply-To: <30a3dd41-2e1c-8658-b83d-8632944d1709@denx.de>
On Tue, 2016-12-06 at 10:01 +0100, Stefano Babic wrote:
> Hi Patrick,
>
> On 30/11/2016 15:59, Patrick Ohly wrote:
> > I've started a Wiki page
> > https://wiki.yoctoproject.org/wiki/System_Update - rudimentary at the
> > moment, but might as well be mentioned already now.
>
> I have seen Mariano added an entry for SWUpdate, too, thanks - I would
> like to edit for better explanation on some parts. Should I try to edit
> directly the page or is it better to discuss it here ?
Use your own judgment. If its uncontroversial, the feel free to edit the
page directly, otherwise let's discuss it here.
If feel that putting information directly into the table is too limiting
(it should be brief), then feel free to start a complete section about
SWUpdate.
I'll do the same for swupd. Editing the sections should be possible
without conflicts, we just have to be more careful about editing the
table concurrently.
--
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.
next prev parent reply other threads:[~2016-12-06 9:45 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 [this message]
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
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=1481017522.17535.38.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=git@andred.net \
--cc=mariano.lopez@intel.com \
--cc=sbabic@denx.de \
--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.