Vanilla 5 - branded 0 :)
Shane, Dongxiao and Alex: from an implementation point of view, I guess
this means eliminating any hardcoded UI-related values (button colours and
styles, for example). Joshua: if you have a rough idea of the things that
will need to be changed from the work you did before
On 06/08/2012 07:28 AM, Barros Pena, Belen wrote:
> Vanilla 5 - branded 0 :)
>
> Shane, Dongxiao and Alex: from an implementation point of view, I guess
> this means eliminating any hardcoded UI-related values (button colours and
> styles, for example).
GTK should be able to pull those colors and
To support the basic workflow of trivial patches:
git format-patch HEAD~.. ; git send-email --to f...@bar.com 0001-foo.patch
We don't want git status reporting on patches lying in the top
level dir in this case.
Cc: Richard Purdie
Signed-off-by: Paul Gortmaker
---
.gitignore |1 +
1 file
On 08/06/12 07:28, Barros Pena, Belen wrote:
> Vanilla 5 - branded 0 :)
>
> Shane, Dongxiao and Alex: from an implementation point of view, I guess
> this means eliminating any hardcoded UI-related values (button
colours and
> styles, for example). Joshua: if you have a rough idea of the things
On 8 June 2012 17:41, Joshua Lock wrote:
>> Joshua: if you have a rough idea of the things that
>> will need to be changed from the work you did before the 1.2 release,
>> please let us know.
I think it's fair that I take over from Joshua as "resident GTK+
knowledge base", having written several
On 08/06/12 13:24, Burton, Ross wrote:
On 8 June 2012 17:41, Joshua Lock wrote:
Joshua: if you have a rough idea of the things that
will need to be changed from the work you did before the 1.2 release,
please let us know.
I think it's fair that I take over from Joshua as "resident GTK+
knowle
On 8 June 2012 21:26, Joshua Lock wrote:
> Even more importantly, being my "go to" guy for GTK+ lore!
What you never knew is that I just asked Emmanuele your question. ;)
Ross
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org
By the way, if there is no theme set, will the app use a reasonable default?
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 8 June 2012 21:42, Stewart, David C wrote:
> By the way, if there is no theme set, will the app use a reasonable default?
It's very hard to not have a theme set. In GNOME the default is
Adwaita (GNOME 3) or Clearlooks (GNOME 2). Many reasonable
distributions of KDE ship a theming bridge so G
From: Nitin A Kamble
The following changes since commit 0612cf3fcb3365e7721a2d5c331f8cd2647ae60b:
hob2: create a standalone deploy image tool (2012-06-08 12:13:43 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib master+work
http://git.pokylinux.org/cgit.
From: Nitin A Kamble
perl needs eglibc to build. The presence of runtime dependency of
perl for eglibc-mtrace caused bitbake to build perl before eglibc,
which causes build failure of perl with poky-tiny distro
This fixes bug: [YOCTO #2523]
Signed-off-by: Nitin A Kamble
---
meta/recipes-cor
From: Nitin A Kamble
resending with corrected contrib branch.
The following changes since commit 0612cf3fcb3365e7721a2d5c331f8cd2647ae60b:
hob2: create a standalone deploy image tool (2012-06-08 12:13:43 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ma
From: Nitin A Kamble
perl needs eglibc to build. The presence of runtime dependency of
perl for eglibc-mtrace caused bitbake to build perl before eglibc,
which causes build failure of perl with poky-tiny distro
This fixes bug: [YOCTO #2523]
Signed-off-by: Nitin A Kamble
---
meta/recipes-cor
On 06/08/2012 03:23 PM, nitin.a.kam...@intel.com wrote:
> From: Nitin A Kamble
>
> perl needs eglibc to build.
> The presence of runtime dependency of
> perl for eglibc-mtrace caused bitbake to build perl before eglibc,
> which causes build failure of perl with poky-tiny distro
>
So is this a
14 matches
Mail list logo
