From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org, Scott Rifenbark <srifenbark@gmail.com>
Subject: Re: wic status
Date: Thu, 17 Jul 2014 09:18:31 -0500 [thread overview]
Message-ID: <1405606711.31082.12.camel@empanada> (raw)
In-Reply-To: <3342528.IHg5slGbJt@peggleto-mobl5.ger.corp.intel.com>
On Thu, 2014-07-17 at 14:51 +0100, Paul Eggleton wrote:
> On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote:
> > On Thu, Jul 17, 2014 at 3:56 PM, Paul Eggleton <
> > paul.eggleton@linux.intel.com> wrote:
> > > On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote:
> > > > There used to be an entry about wic in development manual back in 1.5.2:
> > > > http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html
> > > >
> > > > This entry is gone in current documentation and there seems to be no
> > > > mention of wic at all:
> > > > https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html
> > >
> > > Scott, can you take a look at this if you haven't already?
> >
> > wic was documented in the 1.5.x set and was not put into the 1.6 set. I
> > was told that it was going to change or be further completed so it did not
> > go in that development branch. Wic was never documented in the 1.6 set.
>
> Well, wic is still a part of the system in 1.6 and beyond so we do need to
> document it; as far as I can tell what was in the 1.5 manual linked above
> should be perfectly fine and we can just extend / update it as needed. Tom
> should be able to help fill in any blanks.
>
Right, wic is still included in the system, and like the rest of the
system is undergoing continual development, so I'm not sure why it would
be treated differently.
In any case, to make it easier for users and to avoid a mismatch with
external documentation, over the past couple weeks I've submitted a set
of patches (which have now been merged) that puts most of the help
content into the tool itself, which is all now accessible via 'wic
help'.
Thanks,
Tom
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
next prev parent reply other threads:[~2014-07-17 14:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 12:25 wic status Maciek Borzecki
2014-07-17 12:46 ` Philip Balister
2014-07-17 12:56 ` Paul Eggleton
[not found] ` <CAFNP8Os559bt59bx6tfqp+R+HyUxz66kaxjuvzBGiRKbdUMjdQ@mail.gmail.com>
2014-07-17 13:51 ` Paul Eggleton
2014-07-17 14:06 ` Tom Zanussi
2014-07-17 14:18 ` Tom Zanussi [this message]
2014-07-17 17:38 ` Maciek Borzecki
2014-07-17 18:28 ` Rifenbark, Scott M
2014-07-17 20:07 ` Tom Zanussi
2014-07-18 14:12 ` Maciek Borzecki
2014-07-17 13:52 ` Maciek Borzecki
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=1405606711.31082.12.camel@empanada \
--to=tom.zanussi@linux.intel.com \
--cc=paul.eggleton@linux.intel.com \
--cc=srifenbark@gmail.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.