From: "Eric Bénard" <eric@eukrea.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] qt4.inc: package qtdemo's docs in a separate package
Date: Thu, 15 Sep 2011 18:08:05 +0200 [thread overview]
Message-ID: <4E7222E5.6070401@eukrea.com> (raw)
In-Reply-To: <1316078776-19890-2-git-send-email-denis@eukrea.com>
Hi,
Le 15/09/2011 11:26, Denis Carikli a écrit :
> The documentation was 285M and doesn't fit on the NAND of many machines,
> but in another had part of the documentation is needed for the
> QT demos, so we split the documentation: so qt demo only RRECOMMAND
> the documentation that it really needs.
>
> Thanks to Eric Bénard for explaining me how to split it.
>
and in fact after testing, my initial guess was wrong so Denis will post an
updated patch which works.
Eric
next prev parent reply other threads:[~2011-09-15 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 9:26 Some QT patches Denis Carikli
2011-09-15 9:26 ` [PATCH 1/2] qt4.inc: package qtdemo's docs in a separate package Denis Carikli
2011-09-15 16:08 ` Eric Bénard [this message]
2011-09-15 16:19 ` [PATCH v2] " Denis Carikli
2011-09-15 9:26 ` [PATCH 2/2] qt4(embedded and x11): disable neon for armv6-vfp Denis Carikli
2011-09-16 1:31 ` Marc Reilly
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=4E7222E5.6070401@eukrea.com \
--to=eric@eukrea.com \
--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